From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: 36735@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 [thread overview]
Message-ID: <87zhl0bhru.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87d0i5pk13.fsf@dick.i-did-not-set--mail-host-address--so-tickle-me> (dick's message of "Fri, 19 Jul 2019 21:33:12 -0400")
merge 36735 36736 36737
quit
dick <priapushk@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?
prev parent reply other threads:[~2019-07-26 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-20 1:33 bug#36735: 25.1; gnus-topic-mode clobbers gnus-group-change-level-function dick
2019-07-26 21:36 ` Eric Abrahamsen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zhl0bhru.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=36735@debbugs.gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.