From: "N. Jackson" <nljlistbox2@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: 33140@debbugs.gnu.org
Subject: bug#33140: 27.0.50; `gnus-posting-styles' sees nil ‘message-reply-headers’ variable
Date: Thu, 06 Dec 2018 20:57:05 -0500 [thread overview]
Message-ID: <87k1kmgkum.fsf@moondust.localdomain> (raw)
In-Reply-To: <87y393y9sh.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Wed, 05 Dec 2018 12:54:06 -0800")
At 12:54 -0800 on Wednesday 2018-12-05, Eric Abrahamsen wrote:
> "N. Jackson" <nljlistbox2@gmail.com> writes:
>
>> I'm trying to set up a Gnus posting style that makes use of the
>> ‘message-reply-headers’ variable, but the behaviour I see indicates that
>> this variable is always nil (in the context where the posting styles are
>> evaluated).
>>
>> It seems (this is a wild guess) that the function
>> `gnus-configure-posting-styles' that applies the posting styles that
>> match, and which is called from `message-mode-hook' (I believe), is
>> called before `message-reply-headers' is set.
>>
>> Either that, or `gnus-configure-posting-styles' is evaluated in the
>> context of the wrong buffer (`message-reply-headers' is buffer local to
>> the *unsent reply...* buffer).
>
> So far as I can tell, the problem is the former --
> `gnus-configure-posting-styles' is called before `message-reply-headers'
> is set.
>
> Both `message-reply' and `message-followup' first call
> `message-pop-to-buffer' (which ends up calling `message-mode' and thus
> the `message-mode-hooks', and thus `gnus-configure-posting-styles').
>
> Then they set `message-reply-headers'.
>
> Then they call `message-setup', which calls `message-setup-1', which
> runs the `message-setup-hook', which would be a spot where
> `message-reply-headers' would be accessible.
>
> I will check and see if this changed sometime recently.
I haven't been able to convince myself that `message-reply-headers' can
ever have worked properly with Gnus posting styles.
> I would say that posting-style configuration could be moved to the
> `message-setup-hook',
That sounds right, I think.
> except that that would be guaranteed to wreck all manner of existing
> configurations and get us lots of angry emails.
Maybe. I haven't been able to think of how it would negatively affect
existing setups, but probably I'm just lacking in imagination!
next prev parent reply other threads:[~2018-12-07 1:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 16:03 bug#33140: 27.0.50; `gnus-posting-styles' sees nil ‘message-reply-headers’ variable N. Jackson
2018-12-05 20:54 ` Eric Abrahamsen
2018-12-05 21:05 ` Glenn Morris
2018-12-05 21:13 ` Eric Abrahamsen
2018-12-07 1:57 ` N. Jackson [this message]
2018-12-07 3:17 ` Eric Abrahamsen
2018-12-07 3:22 ` Eric Abrahamsen
2019-05-13 20:40 ` Lars Ingebrigtsen
2019-05-16 18:36 ` Eric Abrahamsen
2019-06-22 13:24 ` Lars Ingebrigtsen
2019-01-10 22:47 ` Óscar Fuentes
2019-09-22 22:47 ` 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=87k1kmgkum.fsf@moondust.localdomain \
--to=nljlistbox2@gmail.com \
--cc=33140@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
/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).