From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: How can I protect the gnus structure?
Date: Mon, 11 Feb 2019 12:05:00 -0800 [thread overview]
Message-ID: <875ztqozv7.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87a7j2ce3k.fsf@chopper>
joakim@verona.se writes:
> Hello,
>
> I misstakenly kill and/or unsubscribe groups pretty often.
> Also I randomly seem to press TAB, breaking my gnus topic structure.
>
> I would like to have some way to guard against such changes, perhaps
> with a prompt. Any idea how to do this?
That happened to me a lot, and I did this:
(eval-after-load "gnus-topic"
'(progn
(define-key gnus-topic-mode-map [tab] nil)
(define-key gnus-topic-mode-map "\C-i" nil)
;; I keep deleting groups by accident.
(define-key gnus-topic-mode-map (kbd "C-k") nil)
(define-key gnus-topic-mode-map (kbd "c") nil)
(define-key gnus-topic-mode-map (kbd "C c") #'gnus-topic-catchup-articles)))
next prev parent reply other threads:[~2019-02-11 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 19:35 joakim
2019-02-11 20:05 ` Eric Abrahamsen [this message]
2019-02-11 20:39 ` joakim
2019-02-11 20:14 ` Emanuel Berg
2019-02-11 20:14 ` Emanuel Berg
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=875ztqozv7.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=info-gnus-english@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.
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 NNTP newsgroup(s).