From: Jeff Senn <senn@maya.com>
Subject: Re: nit with posting styles/followup
Date: 05 Jun 2000 09:28:00 -0400 [thread overview]
Message-ID: <itvojlzz.fsf@SNIPE.maya.com> (raw)
In-Reply-To: dsg@mitre.org's message of "02 Jun 2000 12:36:37 -0400"
dsg@mitre.org (David S. Goldberg) writes:
> I think you want to look at message-dont-reply-to-names rather than
> posting-styles for this particular problem.
Yes -- I could use that to fix (hack around) my problem.
I actually have 2 problems:
1) (address ...) and (name ...) don't seem to work in the posting style
[I worked around this by resorting to adding a ("From: ...")]
2) message doesn't correctly ignore the styled address in follow-ups
[this may well be a side effect of #1 -- and as David points out I
could almost fix this using message-dont-reply-to-names]
Q: Does anyone successfully use (address ...) in posting styles and
have success with 'message' putting in the correct address?
debug-on-entry-ly,
-Jas
prev parent reply other threads:[~2000-06-05 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-01 19:34 Jeff Senn
2000-06-02 16:36 ` David S. Goldberg
2000-06-05 13:28 ` Jeff Senn [this message]
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=itvojlzz.fsf@SNIPE.maya.com \
--to=senn@maya.com \
/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).