Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: show attachments on the top
Date: Sat, 08 Feb 2014 14:23:37 +0800	[thread overview]
Message-ID: <87d2iyktqu.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <b4meh3hkhqc.fsf@jpl.org>

Katsumi Yamaoka <yamaoka@jpl.org> writes:

> Lars Ingebrigtsen wrote:
>> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>
>>> Maybe no one will add a MIME part in this way; people (or almost
>>> mail clients) add attachments at the bottom no matter how the body
>>> is big.  Because of this, I sometimes overlook them.
>>>
>>> The code in this attachment makes Gnus show attachments at the top.
>>> `g' toggles the appearance.
>
>> Making the attachments more visible is a good idea.  Would it make sense
>> to add a new "header" in the display that just lists them?
>
>> Attachments: [button] [button] [button]
>
>> They could also be included where they are in the message like now, but
>> listing them twice shouldn't be a problem...
>
> Thanks for the suggestion.  I've implemented this in the Gnus Git
> master.  Now the feature is turned on by default.  If you don't
> want it, set `gnus-mime-display-attachment-buttons-in-header' to
> nil.
>
> If you have the old code in your .gnus.el file, please remove it
> anyway.  Customize `gnus-header-face-alist' as follows if you
> want to change the appearance of buttons:
>
> (eval-after-load "gnus-art"
>   '(add-to-list
>     'gnus-header-face-alist
>     '("Attachments?:" Header-Name-Face Header-Content-Face)))
>
> When you customize it, note that the element that begins with
> "" should be the last item of `gnus-header-face-alist'.

I really like this change! One thing that seems a bit broken now,
though, is hitting "K o" from the summary buffer --
gnus-article-save-part. I tried it on a few different messages, and they
all gave me the same error, below. I haven't customized much in this
area, so I assume it's not a local issue, but let me know if you want
more information.

Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p "2")
  gnus-article-part-wrapper(nil mm-save-part)
  gnus-article-save-part(nil)
  call-interactively(gnus-article-save-part nil nil)

Thanks,
Eric




  reply	other threads:[~2014-02-08  6:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 10:32 Katsumi Yamaoka
2013-11-01 11:27 ` Julien Danjou
2013-12-26 16:52 ` Lars Ingebrigtsen
2014-02-05  9:54   ` Katsumi Yamaoka
2014-02-08  6:23     ` Eric Abrahamsen [this message]
2014-02-08 10:55       ` Katsumi Yamaoka
2014-02-08 12:20         ` Eric Abrahamsen
2014-02-10  0:19           ` Katsumi Yamaoka
2014-02-10  5:46             ` Eric Abrahamsen
2014-03-05 17:42       ` Lars Ingebrigtsen
2014-01-17 18:29 ` Uwe Brauer
2014-01-18  8:13   ` Gijs Hillenius
2014-01-18 12:41   ` Katsumi Yamaoka
2014-01-19 23:30     ` Katsumi Yamaoka
2014-01-21 11:09       ` Uwe Brauer
2014-01-21 23:55         ` Katsumi Yamaoka
2014-01-22 11:18           ` Uwe Brauer
2014-01-23  2:09             ` Katsumi Yamaoka
2014-01-23  8:04               ` Gijs Hillenius
2014-01-23 10:37                 ` Katsumi Yamaoka
2014-01-23 13:46               ` Uwe Brauer

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=87d2iyktqu.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).