Re: Picking Nits (sgnus v0.79/tm7.52)

[Lars Magne Ingebrigtsen <larsi@ifi.uio.no>]

Steven L Baur <steve@miranova.com> writes:

> 2.  I don't care for the sequence of events when one selects a mail
>     response function.  The subject prompt comes first, and the text
>     is poorly worded -- it should just ask for a Subject:.  The
>     currently selected article then disappears.  Very often I end up
>     splitting the frame and putting the *Article ... buffer in the
>     other window.  This is what Gnus used to do, and I guess I miss
>     it.  The least you could do would be to make the *Article* buffer
>     be the default target for C-X 4 b or C-X 5 b ...

Uhm...  Are you ever prompted for anything when using message.el?  I
thought those prompts had gone the ways of the dinosaurs.  What
commands prompt?

>     The default destination for B c doesn't work at all the way I
>     like.  I don't mind having to type in a destination the first
>     time, but I think Gnus should remember what I've typed the next
>     time this operation is done.

Yup.  It used the wrong variable to store the default in.  Fix in
0.80. 

> 5.  Message mode definitely needs a customized toolbar.  

Definitely.  Luis?  Whoo-hoo!  :-)

> 6.  Marking articles and then running X u has a conflict with Tm and
>     inline image display that I haven't figured out how to defeat yet.
>     I only want to see inline images if I select a single article for
>     viewing.  In mass operations off the X keymap, I just want the
>     decoding to occur and nothing else.

I think the `gnus-summary-display-article-function' variable is what's
used to trigger the tm-ish things, so perhaps the gnus-uu function
could just bind that variable to bypass tm when decoding?  Yes, I
think that should work.

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."