Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@srce.hr>
Cc: ding@gnus.org
Subject: Re: `b'
Date: 19 Nov 1998 12:11:44 +0100	[thread overview]
Message-ID: <kig90h8543z.fsf@jagor.srce.hr> (raw)
In-Reply-To: François Pinard's message of "18 Nov 1998 19:43:07 -0500"


François Pinard <pinard@iro.umontreal.ca> writes:

> > In a true MIME-viewing mode, `o' should save only the message
> > body, one should be able to access the unhacked headers, uuencoded
> > messages should work just like they do with regular buttons, etc.
> > [...]  I'd like for instance `o' to save the messages without the
> > (bogus) headers.  I would also prefer headers not to be inherited
> > and shown.
> 
> `C-d' does not attempt to trigger a MIME-viewing mode.

I know.  I would prefer if it did trigger a Summary-based MIME viewing 
mode, but I've obviously lost that battle.

> > For the latter, I'd like the code to use the existing Gnus MIME
> > engine (the mm-* stuff), so that it works for uuencoded files,
> > etc.
> 
> I think, I may be biased (:-), that `C-d' does its job well, and
> even, that the code is not so badly written.  Maybe it could do
> better now using `mm-*' stuff?  Such `mm-*' did not exist at the
> time `C-d' became able to split MIME parts, and `C-d' has most
> probably not been reevaluated since then.  You say that using `mm-*'
> will give us `uuencoded' parts?  Anything else?

mm- code might be more correct about various other MIME thingies that
come into play over time.  And the code is already conceived as a
library.  Long-term, I think it would simply make more sense to use it 
rather than the home-grown stuff.  It's only a wish, though.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Nostalgia isn't what it used to be.


  parent reply	other threads:[~1998-11-19 11:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-13  0:53 `b' Lars Magne Ingebrigtsen
1998-10-13  2:04 ` `b' Jason R Mastaler
1998-10-13 15:30 ` `b' Simon Josefsson
1998-10-13 16:39   ` `b' Kai Grossjohann
1998-10-13 17:08     ` `b' Simon Josefsson
1998-10-14  8:23       ` `b' Lee Willis
1998-10-14  9:57       ` `b' Kai Grossjohann
1998-10-14 10:33         ` `b' Hrvoje Niksic
1998-10-30  3:00           ` `b' François Pinard
1998-10-30  3:05             ` `b' Hrvoje Niksic
1998-11-01  0:22               ` `b' Kai Grossjohann
1998-11-01  0:54                 ` `b' Hrvoje Niksic
1998-11-01 13:03                   ` `b' Kai Grossjohann
1998-11-01 20:59                     ` `b' Hrvoje Niksic
1998-11-07 14:05                       ` `b' Lars Magne Ingebrigtsen
1998-11-19  0:43               ` `b' François Pinard
1998-11-19  6:00                 ` `b' Lars Magne Ingebrigtsen
1998-11-19 11:32                   ` `b' Hrvoje Niksic
1998-11-19 11:11                 ` Hrvoje Niksic [this message]
1998-10-14 14:01         ` `b' Simon Josefsson
1998-10-14 20:51           ` `b' Kai Grossjohann
1998-10-15 12:47             ` `b' Simon Josefsson
1998-10-17 20:27               ` `b' Lars Magne Ingebrigtsen
1998-10-17 20:29             ` `b' Lars Magne Ingebrigtsen
1998-10-17 20:25   ` `b' Lars Magne Ingebrigtsen

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=kig90h8543z.fsf@jagor.srce.hr \
    --to=hniksic@srce.hr \
    --cc=ding@gnus.org \
    /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).