From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: [9fans] sam enhancement
Date: Wed, 18 Feb 2004 02:07:19 +0100 [thread overview]
Message-ID: <032c01c3f5bb$8fc0c2d0$67844051@SOMA> (raw)
i've been thinking about how too produce simple html
and arbitrary text formatting based on piping the text
through a script.
i think it fits in with the model, i nearly have a first cut
[based on the netlib lunix sam].
the plan is this, on button 2:
- after Search there's another menu entry (if necessary)
- selecting/clicking on it runs the last |cmd on the selected text
so, with a few scripts:
html/i
html/b
...
you can format the text, say:
C/comment
i coded most of it today (when i wasn't coding FPGA drivers).
i think it's a good idea 'cos it fits the model and uses no built
in programability; it's a small amount of code.
i'm very close to having it coded and after it's been tested
i'll post the rcs diffs.
next reply other threads:[~2004-02-18 1:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 1:07 boyd, rounin [this message]
2004-02-18 15:51 ` Rob Pike
2004-02-18 16:42 ` boyd, rounin
2004-02-19 0:04 ` Geoff Collyer
2004-02-19 10:28 ` Wilhelm B. Kloke
2004-02-20 2:10 ` boyd, rounin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='032c01c3f5bb$8fc0c2d0$67844051@SOMA' \
--to=boyd@insultant.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).