GNU bug report logs - #36735
gnus-topic-mode clobbers gnus-group-change-level-function

Previous Next

Full log

View this message in rfc822 format

From: Eric Abrahamsen <eric <at> ericabrahamsen.net>
To: 36735 <at> debbugs.gnu.org 
Subject: bug#36735: 25.1; gnus-topic-mode clobbers gnus-group-change-level-function
Date: Fri, 26 Jul 2019 14:36:05 -0700

merge 36735 36736 36737
quit

dick <priapushk <at> gmail.com> writes:

> emacs -Q --batch -l gnus --eval "(setq gnus-init-inhibit t)" --eval "(setq gnus-current-select-method t)" --eval "(setq gnus-batch-mode t)" --eval "(custom-set-variables '(gnus-startup-file \"/dev/null\") '(gnus-read-newsrc-file nil) '(gnus-select-method (quote (nnnil))) '(gnus-group-change-level-function (lambda (&rest args) (setq foo t))) '(gnus-always-read-dribble-file t) '(gnus-use-dribble-file nil))" --eval "(gnus nil t nil)" --eval "(setq foo nil)" --eval "(gnus-topic-mode)" --eval "(funcall gnus-group-change-level-function \"dummy\" 3 9)" --eval "(cl-assert foo)"

You'll probably need to provide a little more background here before
anyone can help you. I understand that you want Gnus' topic mode to
behave differently than it does, but the whole thing has its own logic,
and changing one bit of that general logic to serve a particular
use-case that you haven't really explained isn't going to motivate
anyone to apply your patch. Not to mention that the patch stands a good
chance of breaking other people's customizations. I previously suggested
you use the gnus-topic-mode-hook to achieve what you want -- did you try
that?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.