Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: attaching many files
Date: Fri, 28 Aug 2009 19:57:10 +0900	[thread overview]
Message-ID: <b4miqg82ol5.fsf@jpl.org> (raw)
In-Reply-To: <b4m7hwyjeyc.fsf@jpl.org>

>>>>> Katsumi Yamaoka wrote:
>>>>>> Reiner Steib wrote:
>> On Thu, Aug 20 2009, Katsumi Yamaoka wrote:

>>> When I attach two or more files to a message, I need to type two
>>> `C-n's every time before attaching the next file.  It is because
>>> the `mml-attach-(file|buffer|external)' commands don't move point
>>> after inserting a tag.  I feel it inconvenience.  Furthermore, if
>>> those commands are invoked at the message header, the tag will be
>>> added to the bottom of the body but point stays in the message
>>> header no matter how big the body may be.  WDYT?

>> I think the behavior when inside the headers is The Right Thing to do.

> Agreed.  Maybe the bottom of the body is the right place especially
> for attachments sent to Windows users.

>> When inside the body, point should probably be moved after the closing
>> mml tag.

> Even when invoking a mml-attach-* command at the message header,
> isn't it better to move point to the closing mml tag?  Currently
> point stays in the header, so a user may not see the tag is added.

I've made changes in the Gnus trunk so that
the `mml-attach-(file|buffer|external)' commands may move point
to the end of a mml tag.  If it causes any trouble, please let me
know.

Regards,



  reply	other threads:[~2009-08-28 10:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-20 11:25 Katsumi Yamaoka
2009-08-20 19:49 ` Reiner Steib
2009-08-20 22:30   ` Katsumi Yamaoka
2009-08-28 10:57     ` Katsumi Yamaoka [this message]
2009-08-28 17:17       ` Reiner Steib
2009-08-30 22:14         ` Katsumi Yamaoka
2009-09-08  6:46           ` Katsumi Yamaoka

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=b4miqg82ol5.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --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).