From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] source code as data not text
Date: Mon, 18 Jun 2001 08:45:16 +0100 [thread overview]
Message-ID: <E15Btj9-0004hu-0K@tele-post-20.mail.demon.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 46 bytes --]
Oh, and the link to SeeSoft is broken too.
[-- Attachment #2: Type: message/rfc822, Size: 2009 bytes --]
From: "Matt" <matt@proweb.co.uk>
To: <9fans@cse.psu.edu>
Subject: [9fans] source code as data not text
Date: Mon, 18 Jun 2001 01:31:13 +0100
Message-ID: <00d701c0f78d$fb26d750$6401a8c0@freeze2k>
Maybe I'm not hard-core enough but one thing I miss is syntax highlighting.
And if you go so far as to parse the source code in the editor then you can
use the opportunity to develop the idea.
There are some good ideas in a paper here http://mindprod.com/scid.html
about source code living in a database rather than a plain text file.
The basic premise is that when an editor knows about what source code is and
does it can offer new views of it etc.
Anyone got any views of their own?
matt
next reply other threads:[~2001-06-18 7:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-18 7:45 nigel [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-28 21:17 Boyd Roberts
[not found] <dhog@plan9.bell-labs.com>
2001-06-18 18:48 ` David Gordon Hogan
2001-06-18 21:31 ` Steve Kilbane
2001-06-19 21:03 ` Richard Elberger
2001-06-19 21:31 ` Steve Kilbane
2001-06-19 7:36 ` Richard Elberger
2001-06-28 22:17 ` Boyd Roberts
2001-06-18 15:24 anothy
2001-06-19 3:52 ` Richard Elberger
2001-06-18 14:45 anothy
2001-06-19 16:51 ` Barry
2001-06-18 7:43 nigel
2001-06-18 9:07 ` Laura Creighton
2001-06-28 21:00 ` Boyd Roberts
2001-06-28 22:02 ` Boyd Roberts
2001-06-18 0:31 Matt
2001-06-18 8:52 ` Laura Creighton
2001-06-18 9:13 ` Matt
2001-06-18 10:02 ` Richard Elberger
2001-06-18 14:56 ` Dan Cross
2001-06-28 21:56 ` Boyd Roberts
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=E15Btj9-0004hu-0K@tele-post-20.mail.demon.net \
--to=nigel@9fs.org \
--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).