Re: No more buttons by default?

[Lars Magne Ingebrigtsen <larsi@gnus.org>]

Steinar Bang <sb@metis.no> writes:

> Hm... one thing I've done a lot, is to send stuff like eg. compilation 
> errors as text/plain parts with c-d disposition of attachment.
> 
> The idea has been that the receipient would see the text to read
> inline in the message, but would be provided with buttons to make it
> easy for him to save it to a file.

Right.  But that's not what the RFCs say that the reader should do.

Anyway -- even though I don't like the buttons much, there may be an
argument that it should be easy to handle MIME parts independently.
One way would be to have commands like `o' and `|' (in the article
buffer) work on the part under point -- if you place point on an
image, it's fairly clear that you want to save that image; if you
place point somewhere in the compilation error, you may want to save
just the part that contains the compilation errors.

However, the user must (I think) be given some visual clue as to where 
each parts starts (and stops).  The buttons are too heavy, but can
anyone come up with some other clue that would be less intrusive?

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen