From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 52871@debbugs.gnu.org
Subject: bug#52871: 29.0.50; weird bug with Gnus, can't have "^From" in `message-hidden-header's
Date: Thu, 20 Jan 2022 10:41:32 +0100 [thread overview]
Message-ID: <87ilue4ucz.fsf@gnus.org> (raw)
In-Reply-To: <87fspo65sr.fsf@web.de> (Michael Heerdegen's message of "Sat, 15 Jan 2022 22:35:32 +0100")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> I can reproduce the original recipe.
>
> Lars, did you remove the comment delimiters in
>
> #+begin_src emacs-lisp
> (setq message-hidden-headers '("^Face"
> ;; "^From"
> "^Mail-Copies-To"
> "^References"
> "^X-Draft-From"
> "^X-Face") )
> #+end_src
>
> when you tried to reproduce the issue?
If by that you mean use
(setq message-hidden-headers '("^Face"
"^From"
"^Mail-Copies-To"
"^References"
"^X-Draft-From"
"^X-Face") )
then yes. Perhaps there's some other customisation option that also
affects how this works?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-01-20 9:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 13:24 bug#52871: 29.0.50; weird bug with Gnus, can't have "^From" in `message-hidden-header's Emanuel Berg via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-29 15:24 ` Lars Ingebrigtsen
2021-12-29 17:36 ` Emanuel Berg via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-29 17:43 ` Lars Ingebrigtsen
2021-12-29 18:12 ` Emanuel Berg via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-15 10:05 ` Lars Ingebrigtsen
2022-01-15 21:35 ` Michael Heerdegen
2022-01-20 9:41 ` Lars Ingebrigtsen [this message]
2022-01-20 16:36 ` Michael Heerdegen
2022-01-21 9:15 ` Lars Ingebrigtsen
2022-01-21 10:54 ` Robert Pluim
2022-01-21 13:18 ` 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
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=87ilue4ucz.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=52871@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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).