Gnus development mailing list
 help / color / mirror / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: ding@gnus.org
Subject: Re: About follup headers on usenet
Date: Tue, 15 Jan 2008 23:22:40 -0800	[thread overview]
Message-ID: <200801160722.m0G7MfWs003628@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <v9ve5xpc09.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Mon, 14 Jan 2008 00:00:06 +0100")

Reiner Steib <reinersteib+gmane@imap.cc> writes:

  > On Sun, Jan 13 2008, reader@newsguy.com wrote:
  > 
  > > Reiner Steib <reinersteib+gmane@imap.cc> writes:
  > >> References?  The References header is hidden by default in No Gnus
  > >> when composing a message.  It is inserted when sending the message.
  > >
  > > Thanks... has it always been that way?  I mean in last 2yrs or so?
  > 
  > Since 2004 (but as said before, only in the development version):

And this has the bad property that even if you do
(setq message-hidden-headers nil)

and then remove the "References" header, it will still get added to the
message when the message is sent.
Is this considered a good idea?



  reply	other threads:[~2008-01-16  7:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-11 18:37 reader
2008-01-12  1:06 ` Reiner Steib
2008-01-13 15:16   ` reader
2008-01-13 23:00     ` Reiner Steib
2008-01-16  7:22       ` Dan Nicolaescu [this message]
2008-01-16 18:32         ` Ted Zlatanov
2008-01-16 18:44           ` Dan Nicolaescu
2008-01-16 21:54           ` reader
2008-01-16 22:23             ` Reiner Steib
2008-01-16 21:50         ` Editing References; Bug in ` message-generate-headers'? (was: About follup headers on usenet) Reiner Steib
2010-04-22  8:15           ` Editing References; Bug in ` message-generate-headers'? Andreas Seltenreich
2008-01-13 15:17   ` About follup headers on usenet reader

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=200801160722.m0G7MfWs003628@sallyv1.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --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).