From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Glenn Morris <rgm@gnu.org>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Forwarding mails
Date: Sun, 20 Jan 2008 22:03:25 +0100 [thread overview]
Message-ID: <v9bq7gjjky.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <dutzl844xn.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sun, 20 Jan 2008 15:28:52 -0500")
[ Including ding@gnus, as it's becoming (only) Gnus related. Feel
free to strip emacs-devel on reply. ]
On Sun, Jan 20 2008, Glenn Morris wrote:
> Reiner Steib wrote:
>> Didn't C-d (`gnus-summary-enter-digest-group') work for you?
>
> Yes (in that it sends me to a buffer with two messages, one empty with
> subject (none) from nobody, one the original message);
I can't reproduce this. After one `C-d', I get a summary buffer like
this:
| Martin Svenson bugfix: python.el: completion in inferior python
With another `C-d', I get:
| m n/a Martin Svenson <* mixed> bugfix: python.el: completion [...]
| n/a Martin Svenson <1 text>
| n/a Martin Svenson <2 text> "python-el-completion-fix.patch"
> but I didn't know about that command.
I didn't know that `gnus-summary-enter-digest-group' can handle it,
but after someone mentioned some rmail undigest command, I just tried
it. ;-)
> PS given that Gnus can discard duplicate messages, and the mailing
> list can be set to not send you duplicates anyway,
I'm not subscribed to emacs-devel, I read it via Gmane, so I don't get
duplicates in the first place.
> do you really need to insert a Mail-Followup-To header?
I split Cc-ed mailing list message to special Gnus group, so it's no
big deal to receive Cc's, but they are not necessary for me. If it is
annoying for you, I try to avoid it in the future.
> It means Gnus starts composing my followup as to: rms, which makes
> little sense, since I'm replying to you.
Does `message-dont-reply-to-names' include your name or address? In
this case, Gnus shouldn't reply to you, I think (I'm to lazy to look
into the code).
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2008-01-20 21:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 13:28 [phromo@gmail.com: bugfix: python.el: completion in inferior python] Richard Stallman
2008-01-20 3:58 ` Glenn Morris
2008-01-20 9:19 ` Forwarding mails (was: [phromo@gmail.com: bugfix: python.el: completion in inferior python]) Reiner Steib
2008-01-20 20:28 ` Forwarding mails Glenn Morris
2008-01-20 21:03 ` Reiner Steib [this message]
2008-01-20 9:28 ` [phromo@gmail.com: bugfix: python.el: completion in inferior python] Andreas Schwab
2008-01-20 20:29 ` Glenn Morris
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=v9bq7gjjky.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).