Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: ding@gnus.org
Subject: Editing References; Bug in ` message-generate-headers'? (was: About follup headers on usenet)
Date: Wed, 16 Jan 2008 22:50:33 +0100	[thread overview]
Message-ID: <v9ir1tjv86.fsf_-_@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <200801160722.m0G7MfWs003628@sallyv1.ics.uci.edu> (Dan Nicolaescu's message of "Tue, 15 Jan 2008 23:22:40 -0800")

On Wed, Jan 16 2008, Dan Nicolaescu wrote:

> 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?

There was some discussion abut this:

,----
| Subject: Header im message buffer
| From: Oliver Scholz <alkibia...@gmx.de>
| Date: Mon, 19 Mar 2007 19:27:50 +0100
| Message-ID: <45fed62a$0$20297$9b4e6d93@newsspool3.arcor-online.net>
| Newsgroups: de.comm.software.gnus
`----

Andreas Seltenreich proposed a patch (see below), but I didn't have
time to test it.  Anyone?

,----[ http://thread.gmane.org/87ejnblqf5.fsf@gate450.dyndns.org ]
| From: Andreas Seltenreich <andreas+ding@gate450.dyndns.org>
| Subject: dysfunctional code in message-generate-headers
| To: ding@gnus.org
| Date: Mon, 26 Mar 2007 22:07:26 +0200
| Message-ID: <87ejnblqf5.fsf@gate450.dyndns.org>
| 
| Hi,
| 
| there's some discussion in de.comm.software.gnus about an unintuitive
| behavior of Message.  Currently, a "References" header that was
| inserted on buffer creation and deleted by the user is inserted again
| when the mail is being sent.  There's also an older bug report about
| this: <news:87lkok9nnw.fsf@jidanni.org>.
| 
| Looking at the code, it seems that message-generate-headers already
| has some provision to avoid repeated insertion.  However, the code
| doesn't cause any effect at the moment, as it only puts /non-optional/
| headers into message-inserted-headers, while the check to avoid
| repeated insertion only applies to /optional/ ones.
| 
| This looks like a bug to me, and actually putting optional headers
| into message-inserted-headers as in the attached patch results in the
| behavior desired in the bug reports.
| 
| I'd like to propose this patch for No Gnus for now, since it
| essentially enables an old feature for the first time.  WDYT?
`----

--8<---------------cut here---------------start------------->8---
--- message.el	15 Mar 2007 22:41:21 -0000	7.202
+++ message.el	26 Mar 2007 00:37:08 -0000
@@ -5580,6 +5580,7 @@
 		      (if formatter
 			  (funcall formatter header value)
 			(insert header-string ": " value))
+		      (push header-string message-inserted-headers)
 		      (goto-char (message-fill-field))
 		      ;; We check whether the value was ended by a
 		      ;; newline.  If not, we insert one.
--8<---------------cut here---------------end--------------->8---

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



  parent reply	other threads:[~2008-01-16 21:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-11 18:37 About follup headers on usenet 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
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         ` Reiner Steib [this message]
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=v9ir1tjv86.fsf_-_@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=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).