From: "Adam Sjøgren" <asjo@koldfront.dk>
To: ding@gnus.org
Subject: Re: Posting a draft to a newsgroup stopped(?) working?
Date: Sat, 02 Jan 2021 04:33:18 +0100 [thread overview]
Message-ID: <87k0swm2rl.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87wnwwm5c1.fsf@tullinup.koldfront.dk>
Adam writes:
> Andrew writes:
>
>> Interesting. This is probably an error (I don't think this should have
>> done anything to this header). I will look into it, but do you have more
>> info about exactly what in this patch caused the change?
>
> How do you debug a defmacro?
>
> I'm guessing it is due some of the changes to gnus-setup-message in
> gnus-msg.el (I can't find anywhere else where the header is added), but
> my usual basic trick of M-x edebug-defun is failing me for stepping
> through and trying to figure out what is going on :-)
Ok, so I have printf/(message) debugged a little bit. I'm looking at
this part of gnus-setup-message in gnus-msg.el:
(gnus-alist-pull ',(intern gnus-draft-meta-information-header)
message-required-headers)
(message "ASJO group %s" ,group)
(when (and ,group
(not (string= ,group "")))
(push (cons
(intern gnus-draft-meta-information-header)
(gnus-inews-make-draft (or ,yanked ,article)))
message-required-headers))
(message "ASJO message-requires-headers %s" message-required-headers)
(unwind-protect
If I go to an nntp-group and do a to create a new article, the output
is:
ASJO group nil
ASJO message-requires-headers ((optional . References) From)
If I instead go f to create a follow up, the output is:
ASJO group nntp+gm:gmane.test
ASJO message-requires-headers ((X-Draft-From lambda nil (gnus-inews-make-draft-meta-information nntp+gm:gmane.test '8744)) (optional . References) From)
So I guess group used to be filled in regardless, but now it isn't?!
Best regards,
Adam
--
"I skal gå tre skridt væk fra mig Adam Sjøgren
For jeg har fundet en som rammer" asjo@koldfront.dk
next prev parent reply other threads:[~2021-01-02 3:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-01 19:42 Adam Sjøgren
2021-01-01 20:38 ` Eric Abrahamsen
2021-01-01 20:48 ` Mock Turtle
2021-01-01 20:53 ` Eric Abrahamsen
2021-01-01 21:02 ` Adam Sjøgren
2021-01-01 21:17 ` Mock Turtle
2021-01-01 21:23 ` Eric Abrahamsen
2021-01-01 21:44 ` Adam Sjøgren
2021-01-02 0:18 ` Adam Sjøgren
2021-01-02 0:58 ` Eric Abrahamsen
2021-01-02 1:02 ` Adam Sjøgren
2021-01-02 2:03 ` Adam Sjøgren
2021-01-02 2:14 ` Andrew Cohen
2021-01-02 2:25 ` Adam Sjøgren
2021-01-02 2:37 ` Adam Sjøgren
2021-01-02 3:33 ` Adam Sjøgren [this message]
2021-01-02 3:40 ` Adam Sjøgren
2021-01-02 3:45 ` Adam Sjøgren
2021-01-02 3:52 ` Andrew Cohen
2021-01-02 4:01 ` Adam Sjøgren
2021-01-02 4:02 ` Andrew Cohen
2021-01-02 4:10 ` Adam Sjøgren
2021-01-02 4:32 ` Andrew Cohen
2021-01-02 4:42 ` Adam Sjøgren
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=87k0swm2rl.fsf@tullinup.koldfront.dk \
--to=asjo@koldfront.dk \
--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).