Gnus development mailing list
 help / color / mirror / Atom feed
From: Steven L Baur <steve@miranova.com>
Subject: Re: Suggestions
Date: 02 May 1996 11:07:51 -0700	[thread overview]
Message-ID: <m2g29jhrt4.fsf@deanna.miranova.com> (raw)
In-Reply-To: Kai Grossjohann's message of 02 May 1996 08:29:10 -0700

>>>>> "Kai" == Kai Grossjohann <grossjoh@charly.informatik.uni-dortmund.de> writes:

>>>>> On 02 May 1996 16:31:07 +0200, "Ketil.Z" <ketil@ii.uib.no> said:
Ketil> Anyway, what I'd really like for [SR]Gnus, is to recognize,
Ketil> and do various things with different regions of a message.
Ketil> In particular, I'd like source code to be treated differently
Ketil> from text - perhaps according to defaults in text-mode versus
Ketil> cc-mode (other modes might apply)?

Ketil> Other things, like tables and such would be nice to
Ketil> recognize, too.  I guess the most important problem is
Ketil> knowing when to auto fill, and when not to.

This is a reasonable idea, but well beyond the scope of what Gnus 5.2
or Red Gnus ought to be doing.  There are enough hooks in Gnus to let
one experiment with different ideas.  Hopefully the Gnus API is going
to stabilize thus encouraging this kind of experimentation ...

Kai> I think this problem is AI complete if you want to do it properly.  I
Kai> propose the following view on this:

Kai> The author of a mail message wrote it in a monospaced (as opposed to
Kai> proportional) font.  The author of a message tries to make it
Kai> readable.  Therefore the rendition of a message that the author sees
Kai> can be expected to be rather readable.  Thus you shouldn't
Kai> second-guess that and just use a monospaced font for everything.

Reading mail in a variable width font can be amusing.  It definitely
puts .signature ASCII graphics in their place.  Composing mail is
another story though.

Kai> I'd imagine recognizing C might be rather easy: if the lines ends in
Kai> ";" it's C, if the prev and/or the next line is C and the line
Kai> contains "else", it's C, too.

Kai> But how would you tell the difference between English and Cobol in
Kai> "add a to b giving c"?

You could at least start with the heuristics that file(1) uses.
Another possibility is to extend the categories of MIME types.  I
believe TM already supports an Emacs-LISP text MIME type, for example.

What I would really hate to see is Gnus support of the equivalent of
``WINMAIL.DAT''.
-- 
steve@miranova.com baur
Unsolicited commercial e-mail will be proofread for $250/hour.
Andrea Seastrand: For your vote on the Telecom bill, I will vote for anyone
except you in November.


  reply	other threads:[~1996-05-02 18:07 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   ` Steven L Baur [this message]
1996-05-02 23:46     ` Suggestions Per Abrahamsen
1996-05-03  7:38   ` Suggestions Ketil Z Malde
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=m2g29jhrt4.fsf@deanna.miranova.com \
    --to=steve@miranova.com \
    /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).