Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: drafts group bindings do not match manual?
Date: Mon, 08 Jun 2020 16:23:53 +0100	[thread overview]
Message-ID: <87a71doa2e.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87lfkxmvw6.fsf@ericabrahamsen.net>

On Monday,  8 Jun 2020 at 08:15, Eric Abrahamsen wrote:
> 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 :)

Thanks for the pointer.  I'll have a look.

The thing that confuses me is that the bindings that are "intercepted"
(for want of a better word) are intercepted by gnus itself.  To be more
precise, the bindings are exactly as I would expect in a normal gnus
group.  Although Draft mode is enabled, the bindings for that minor mode
are not.  Hopefully the search mentioned above will help.

Thanks again,
eric

-- 
Eric S Fraga via Emacs 28.0.50 & org 9.3.7 on Debian bullseye/sid



  reply	other threads:[~2020-06-08 15:24 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
2020-06-08 15:23             ` Eric S Fraga [this message]
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=87a71doa2e.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=ding@gnus.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).