From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: 33665@debbugs.gnu.org
Subject: bug#33665: 27.0.50; Variables not set up in Gnus when hooks are run
Date: Wed, 19 Dec 2018 22:57:47 +0100 [thread overview]
Message-ID: <m3efad89ic.fsf@gnus.org> (raw)
In-Reply-To: <874lbiv7xs.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Wed, 12 Dec 2018 11:52:47 -0800")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> On 12/12/18 15:36 PM, Lars Ingebrigtsen wrote:
>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>
>>> Okay. This patch should restore that behavior. I don't see any other
>>> buffer-local variables that were being set to a specific value, other
>>> than `gnus-newsgroup-name'.
>>
>> I think that looks OK, but I don't understand the:
>>
>> - (setq gnus-newsgroup-name group)
>> +; (setq gnus-newsgroup-name group)
>
> That was just sort of a note to self -- if `gnus-newsgroup-name' is set
> in `gnus-summary-mode' then it doesn't need to be set again in
> `gnus-summary-setup-buffer'. But I was nervous I would break more stuff,
> and couldn't bring myself to actually delete it.
You haven't pushed the fixes yet? Gnus is unusable for me on master as
it is.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2018-12-19 21:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 16:37 bug#33665: 27.0.50; Variables not set up in Gnus when hooks are run Lars Ingebrigtsen
2018-12-07 17:25 ` Eric Abrahamsen
2018-12-07 17:52 ` Eric Abrahamsen
2018-12-07 18:04 ` Lars Ingebrigtsen
2018-12-07 18:36 ` Eric Abrahamsen
2018-12-12 14:36 ` Lars Ingebrigtsen
2018-12-12 19:52 ` Eric Abrahamsen
2018-12-19 21:57 ` Lars Ingebrigtsen [this message]
2018-12-19 22:14 ` Eric Abrahamsen
2018-12-19 22:17 ` Lars Ingebrigtsen
2018-12-19 22:30 ` Eric Abrahamsen
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=m3efad89ic.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=33665@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).