From: Ketil Z Malde <ketil@ii.uib.no>
Cc: "Ketil.Z" <ketil@ii.uib.no>, ding@ifi.uio.no
Subject: Re: Suggestions
Date: 03 May 1996 09:38:15 +0200 [thread overview]
Message-ID: <KETIL-egwx2u5hqw.fsf@vipe.ii.uib.no> (raw)
In-Reply-To: Kai Grossjohann's message of 02 May 1996 17:29:10 +0200
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1823 bytes --]
Kai Grossjohann <grossjoh@ls6.informatik.uni-dortmund.de> writes:
> I think this problem is AI complete if you want to do it properly.
Well, I was planning on settling for non-proper solutions, then.
> The author of a mail message wrote it in a monospaced (as opposed to
> proportional) font. The author of a message tries to make it
> readable.
...but then he shouldn't use a monospaced font! :-)
Besides, that's not really the issue -- the issue is when to break
lines, and when not to. It's OK to accept things as they come on a 80
column vt100, but I have a fairly large Emacs window, and I'd like to
have text something more than just a narrow column.
I understand that it might be difficult to recognize when things can't
be broken, but some heuristics I'd suggest would be:
o lines with very few (non-wsp) characters, say less than 30
o lines with lots of non-letters [|\(){},+-*/&%$#]
o lines between «begin 644» and «end» :-)
Perhaps what we really need is for some well chosen SGML tags to get
accepted on Usenet. How about an SGML-hierarchy? RFD sgml.general,
anyone? Have tags like <code>, <text>, <sig>, <footnote>, for instance.
> I'd imagine recognizing C might be rather easy: if the lines ends in
> ";" it's C, if the prev and/or the next line is C and the line
> contains "else", it's C, too.
And wouldn't it be way cool to have this display as any other C-code
(read: cc-mode/font-lock'ed)? I likes it. I likes it a lot.
> But how would you tell the difference between English and Cobol in
> "add a to b giving c"?
..and I'll worry about _that_ when somebody sends me messages with cobol
in them. (Hey, how's font-locking in cobol-mode, anyway? :-)
~kzm
--
Mail from aol.com and interramp.com domains will be discarded
Finger <ketil@haukugle.ii.uib.no> for more info
next prev parent reply other threads:[~1996-05-03 7:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-02 14:31 Suggestions Ketil.Z
1996-05-02 15:29 ` Suggestions Kai Grossjohann
1996-05-02 18:07 ` Suggestions Steven L Baur
1996-05-02 23:46 ` Suggestions Per Abrahamsen
1996-05-03 7:38 ` Ketil Z Malde [this message]
1996-05-03 19:35 ` Suggestions Steven L Baur
1996-05-04 2:02 ` Suggestions Per Abrahamsen
1996-05-04 6:11 ` Suggestions Steven L Baur
1996-05-04 9:33 ` Suggestions Per Abrahamsen
1996-05-05 14:20 ` Suggestions 守岡 知彦 / MORIOKA Tomohiko
1996-05-05 11:37 ` Suggestions Ketil.Z
1996-05-05 13:28 ` Suggestions Per Abrahamsen
1996-05-05 21:49 ` Suggestions Lars Magne Ingebrigtsen
1996-05-05 22:34 ` Suggestions Per Abrahamsen
1996-05-05 23:41 ` Suggestions Steven L Baur
1996-05-05 23:52 ` Suggestions Lars Magne Ingebrigtsen
1996-05-06 5:10 ` Suggestions Jacob Morzinski
1996-05-07 14:15 ` Suggestions Lars Magne Ingebrigtsen
1996-05-07 18:55 ` Suggestions Paul Franklin
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=KETIL-egwx2u5hqw.fsf@vipe.ii.uib.no \
--to=ketil@ii.uib.no \
--cc=ding@ifi.uio.no \
/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).