From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: attaching many files
Date: Thu, 20 Aug 2009 20:25:24 +0900 [thread overview]
Message-ID: <b4meir6pw0r.fsf@jpl.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 616 bytes --]
Hi,
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?
It's easy to make those commands move point. That is to remove
`save-excursion'. Is it ok?
To try the new behavior without modifying Gnus, use the following
advices:
[-- Attachment #2: Type: application/emacs-lisp, Size: 533 bytes --]
next reply other threads:[~2009-08-20 11:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 11:25 Katsumi Yamaoka [this message]
2009-08-20 19:49 ` Reiner Steib
2009-08-20 22:30 ` Katsumi Yamaoka
2009-08-28 10:57 ` Katsumi Yamaoka
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=b4meir6pw0r.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).