From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: ding@gnus.org
Subject: Re: drafts group bindings do not match manual?
Date: Mon, 08 Jun 2020 08:15:21 -0700 [thread overview]
Message-ID: <87lfkxmvw6.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87sgf6aqub.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Mon, 08 Jun 2020 09:45:16 +0100")
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> On Saturday, 6 Jun 2020 at 20:37, Eric S Fraga wrote:
>> Thanks all for feedback as at least I know where to look.
>
> Quick update: no luck. I've looked everywhere in my configuration (both
> Emacs generally and gnus specifically) and have not found anything that
> would affect gnus setting up the Draft mode bindings. I'll keep looking
> as I must have missed something... but at least it's not a deal breaker
> as the functionality is still there obviously, just not bound to the
> keys as was.
If all the proper modes are active, you might take a look at the
(elisp) Searching Keymaps part of the manual -- that shows you all the
variables and overrides that might be intercepting keybindings. Looks
tedious to search through, but I can't think of anything else :)
next prev parent reply other threads:[~2020-06-08 15:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 15:33 Eric S Fraga
2020-06-06 16:13 ` Andreas Schwab
2020-06-06 16:27 ` Eric S Fraga
2020-06-06 16:19 ` Eric Abrahamsen
2020-06-06 16:28 ` Eric S Fraga
2020-06-06 18:36 ` Eric Abrahamsen
2020-06-06 19:37 ` Eric S Fraga
2020-06-08 8:45 ` Eric S Fraga
2020-06-08 15:15 ` Eric Abrahamsen [this message]
2020-06-08 15:23 ` Eric S Fraga
2020-06-08 16:10 ` Andreas Schwab
2020-06-08 19:36 ` Eric S Fraga
2020-06-08 20:14 ` Andreas Schwab
2020-06-09 9:58 ` Eric S Fraga
2020-06-11 20:17 ` David Rogers
2020-06-12 9:43 ` Eric S Fraga
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=87lfkxmvw6.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.org \
--cc=e.fraga@ucl.ac.uk \
/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).