From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/6116 Path: main.gmane.org!not-for-mail From: Ketil Z Malde Newsgroups: gmane.emacs.gnus.general Subject: Re: Suggestions Date: 03 May 1996 09:38:15 +0200 Sender: ketil@ii.uib.no Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035146620 2623 80.91.224.250 (20 Oct 2002 20:43:40 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 20:43:40 +0000 (UTC) Cc: "Ketil.Z" , ding@ifi.uio.no Return-Path: ding-request@ifi.uio.no Original-Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by deanna.miranova.com (8.7.5/8.6.9) with SMTP id BAA26837 for ; Fri, 3 May 1996 01:16:47 -0700 Original-Received: from eik (eik.ii.uib.no [129.177.16.3]) by ifi.uio.no with SMTP (8.6.11/ifi2.4) id for ; Fri, 3 May 1996 09:38:36 +0200 Original-Received: from vipe.ii.uib.no (vipe) by eik with SMTP id AA05144 (5.67b/IDA-1.5 for ding@ifi.uio.no); Fri, 3 May 1996 09:38:30 +0200 Original-Received: by vipe.ii.uib.no; (5.65/1.1.8.2/08Jun94-0756AM) id AA05701; Fri, 3 May 1996 09:38:29 +0200 Original-To: Kai Grossjohann In-Reply-To: Kai Grossjohann's message of 02 May 1996 17:29:10 +0200 Original-Lines: 45 X-Mailer: September Gnus v0.76/XEmacs 19.14 Xref: main.gmane.org gmane.emacs.gnus.general:6116 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:6116 Kai Grossjohann 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 , , , , 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 for more info