From: "Matt" <matt@proweb.co.uk>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] source code as data not text
Date: Mon, 18 Jun 2001 10:13:57 +0100 [thread overview]
Message-ID: <010d01c0f7d7$013abd70$6401a8c0@freeze2k> (raw)
In-Reply-To: <200106180852.KAA04199@boris.cd.chalmers.se>
bah, my fault but I wasn't really thinking about the database side of
things. Changing the file format is definately a no-no.
What sparked my interest was making the editor do more work.
Maybe it's because I write code that writes code and having string literals
in a different colour from the source code helps me see.
I did like VB's auto parsing if input code. Highlighting a sections that are
stynax errors etc. must reduce the cycle?
I'm glad I asked here though. Can't think of a better bunch of people to run
it past.
matt
next prev parent reply other threads:[~2001-06-18 9:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-18 0:31 Matt
2001-06-18 8:52 ` Laura Creighton
2001-06-18 9:13 ` Matt [this message]
2001-06-18 10:02 ` Richard Elberger
2001-06-18 14:56 ` Dan Cross
2001-06-28 21:56 ` Boyd Roberts
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 7:45 nigel
2001-06-18 14:45 anothy
2001-06-19 16:51 ` Barry
2001-06-18 15:24 anothy
2001-06-19 3:52 ` Richard Elberger
[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-28 21:17 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='010d01c0f7d7$013abd70$6401a8c0@freeze2k' \
--to=matt@proweb.co.uk \
--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).