Gnus development mailing list
 help / color / mirror / Atom feed
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: Sat, 06 Jun 2020 11:36:22 -0700	[thread overview]
Message-ID: <871rmst521.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <875zc4cg59.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Sat, 06 Jun 2020 17:28:50 +0100")

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

> On Saturday,  6 Jun 2020 at 09:19, Eric Abrahamsen wrote:
>> I've always just hit "e", I didn't know "D e" was supposed to work.
>> But it does work here, sorry...
>
> I also used to use "e" but that stopped working.  That's how I found out
> about "D e" (and other D commands).
>
> It really looks like gnus is treating the drafts group like any other
> group now whereas it is meant to be special (and hence have different
> bindings).
>
> May have to go look at the code, I guess!

First thing would be to check that gnus-draft-mode is among the minor
modes active in your draft group, and that, if you do "G p" on the draft
group in your *Groups* buffer, you see:

((gnus-dummy
  (gnus-draft-mode)))


  reply	other threads:[~2020-06-06 18:37 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 [this message]
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
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=871rmst521.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).