From: Chong Yidong <cyd@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 11941@debbugs.gnu.org
Subject: bug#11941: 24.1.50; Error in debbugs-gnu with gnus-inews-do-gcc
Date: Wed, 26 Dec 2012 10:47:53 +0800 [thread overview]
Message-ID: <87liclsf52.fsf@gnu.org> (raw)
In-Reply-To: <878v8m3uu4.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 25 Dec 2012 18:28:03 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
>> Similarly, on Emacs 24.2 when I respond from a debbugs group, the Gcc
>> header is also
>>
>> Gcc: nnfolder+archive:sent.2012-09
>>
>> On trunk, when I respond from a debbugs group, the Gcc header is the
>> faulty one given above.
>
> The Gcc header is inserted by `gnus-inews-insert-gcc'. I've traced
> through the function, and the following form is the one evaluated to
> insert the group name.
>
> (gnus-group-prefixed-name "sent.2012-09" gnus-message-archive-method)
>
> What does it eval to for you?
Evaluating this in the (Message mode) reply buffer, evaluating the above
gives "sent.2012-09". Evaluating `gnus-message-archive-method' gives
"archive". Looking through the `gnus-group-prefixed-name' function, I
see that this happens because
(gnus-server-to-method "archive")
returns nil. Perhaps because some part of Gnus has not been
initialized? (I did not run M-x gnus before using debbug-gnus.)
Am I to understand that you can't reproduce this? It is 100%
reproducible for me.
next prev parent reply other threads:[~2012-12-26 2:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-14 5:28 bug#11941: 24.1.50; Error in debbugs-gnu with gnus-inews-do-gcc Chong Yidong
2012-07-17 10:22 ` Michael Albinus
2012-07-29 23:06 ` Glenn Morris
2012-07-31 7:47 ` Michael Albinus
2012-09-05 19:06 ` Lars Ingebrigtsen
2012-09-05 19:08 ` Lars Ingebrigtsen
2012-09-06 4:07 ` Chong Yidong
2012-09-06 14:11 ` Lars Ingebrigtsen
2012-09-07 4:26 ` Chong Yidong
2012-12-25 17:28 ` Lars Ingebrigtsen
2012-12-26 2:47 ` Chong Yidong [this message]
2012-12-26 13:25 ` Lars Ingebrigtsen
2012-12-31 17:02 ` Lars Magne Ingebrigtsen
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=87liclsf52.fsf@gnu.org \
--to=cyd@gnu.org \
--cc=11941@debbugs.gnu.org \
--cc=larsi@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.
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).