unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: "N. Jackson" <nljlistbox2@gmail.com>
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 19:17:09 -0800	[thread overview]
Message-ID: <87h8fqxbyi.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87k1kmgkum.fsf@moondust.localdomain> (N. Jackson's message of "Thu, 06 Dec 2018 20:57:05 -0500")

"N. Jackson" <nljlistbox2@gmail.com> writes:

> At 12:54 -0800 on Wednesday 2018-12-05, Eric Abrahamsen wrote:
>
>> "N. Jackson" <nljlistbox2@gmail.com> writes:
>>

[...]

>> 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. 

The other possibility is: `gnus-configure-posting-styles' adds all its
actions to `message-setup-hook'. Perhaps the way it's meant to work is:
g-c-p-s adds *forms* to the message-setup-hook, but those forms aren't
actually evaluated until the hook is running, at which point we should
have access to everything we need.

I would need to look more closely at it to tell if that's the case, or
if it *could* be the case, but it would be one way that this code might
once have worked.

>> 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!

You'd be amazed at the number of ways things can blow up!





  reply	other threads:[~2018-12-07  3:17 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
2018-12-07  3:17     ` Eric Abrahamsen [this message]
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=87h8fqxbyi.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=33140@debbugs.gnu.org \
    --cc=nljlistbox2@gmail.com \
    /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).