From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: Bug in Wide Reply?
Date: Mon, 10 Feb 2003 18:45:10 +0100 [thread overview]
Message-ID: <v9wuk8f2s9.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3n0l46p3y.fsf@radon.sourcefire.com> (Chris Green's message of "Mon, 10 Feb 2003 12:07:45 -0500")
On Mon, Feb 10 2003, Chris Green wrote:
> From: Jennifer Steffens <jennifer.steffens@sourcefire.com>
> Subject: etc....
> To: Brian Caswell <bmc@gandalf.sourcefire.com>, Chris Green
> <cmg@sourcefire.com>
> CC: Kristi Burgess <kristi.burgess@sourcefire.com>
>
> When I do a
>
> S W, S V, or F,
>
> The resultant buffer starts out with:
>
> To: Jennifer Steffens <jennifer.steffens@sourcefire.com>
> Cc: Brian Caswell <bmc@gandalf.sourcefire.com>
>
> and Poor old Kristi is left from the rest of the headers.
Works for me. `f' gives me:
,----
| To: Jennifer Steffens <jennifer.steffens@sourcefire.com>
| Cc: Brian Caswell <bmc@gandalf.sourcefire.com>,
| Chris Green <cmg@sourcefire.com>,
| Kristi Burgess <kristi.burgess@sourcefire.com>
| Subject: Re: etc....
`----
What is the value of `message-dont-reply-to-names'?
,----[ C-h v message-dont-reply-to-names RET ]
| message-dont-reply-to-names's value is [...]
|
| Documentation:
| *A regexp specifying addresses to prune when doing wide replies.
| A value of nil means exclude your own user name only.
|
| You can customize this variable.
|
| Defined in `message'.
`----
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next prev parent reply other threads:[~2003-02-10 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 17:07 Chris Green
2003-02-10 17:45 ` Reiner Steib [this message]
2003-02-10 19:07 ` Chris Green
2003-02-12 14:28 ` Lőrentey Károly
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=v9wuk8f2s9.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.de \
/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).