From: Bob Newell <bobnewell@bobnewell.net>
To: ding@gnus.org
Subject: Re: Space in Gcc name taken as list?
Date: Sat, 13 Nov 2021 06:54:35 -1000 [thread overview]
Message-ID: <87czn4j8s4.fsf@emailmessageidheader.nil> (raw)
In-Reply-To: <87k0hccsgs.fsf@gmail.com> (Robert Pluim's message of "Sat, 13 Nov 2021 10:31:15 +0100")
Robert Pluin:
> In gnus-inews-do-gcc:
>
> (setq groups (message-unquote-tokens
> (message-tokenize-header gcc " ,\n\t")))
>
> I think thatʼs a bug. The separator in mail headers is ',' (but Iʼd
> allow '\n' here just for convenience).
>
> gnus-summary-resend-message-insert-gcc splits on " ,", but then
> inserts with ',' as a separator. I think I rest my case 😁.
>
> Robert
I experimentally changed " ,\n\t" to ",\n\t" and " ," to ","
and everything works as expected. This might be a candidate
for a patch to the master branch if Eric and Lars agree.
Mahalo for your assistance!
--
Bob Newell
Honolulu, Hawai`i
- Via GNU/Linux/Emacs/Gnus/BBDB
next prev parent reply other threads:[~2021-11-13 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 3:23 Bob Newell
2021-11-13 9:31 ` Robert Pluim
2021-11-13 16:54 ` Bob Newell [this message]
2021-11-14 1:22 ` Lars 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87czn4j8s4.fsf@emailmessageidheader.nil \
--to=bobnewell@bobnewell.net \
--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).