Gnus development mailing list
 help / color / mirror / Atom feed
From: David Rogers <davidandrewrogers@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: ding@gnus.org
Subject: Re: drafts group bindings do not match manual?
Date: Thu, 11 Jun 2020 13:17:03 -0700	[thread overview]
Message-ID: <s0e4krhmk74.fsf@gmail.com> (raw)
In-Reply-To: <874krous2v.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Sat, 06 Jun 2020 16:33:44 +0100")

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> Hello all,
>
> when I enter my drafts (nndrafts:drafts) group, the bindings are 
> not
> what the manual would suggest.  Specifically, "D" is bound to
> gnus-summary-mark-as-read-backward.  Instead of being able to 
> type "D e"
> to edit a draft message, I have to type M-x 
> gnus-draft-edit-message
> RET...
>
> I'm using gnus from the latest git Emacs, updated a few minutes 
> ago.
>
> Have I done something wrong somewhere?  (not an uncommon event
> unfortunately but please bear with me...)
>
> Thank you.

There's a bit in the manual advising that, if this particular 
thing happens where the drafts group loses its bindings, the 
solution is supposed to be killing the drafts group (C-k) and 
restarting gnus - did this have no effect?

-- 
David Rogers


  parent reply	other threads:[~2020-06-11 20:18 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
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 [this message]
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=s0e4krhmk74.fsf@gmail.com \
    --to=davidandrewrogers@gmail.com \
    --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).