From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: <ding@gnus.org>
Subject: Re: just use "n" to the very end?
Date: Wed, 23 Apr 2014 12:21:23 +0100 [thread overview]
Message-ID: <87y4ywfg0c.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87d2g83ns9.fsf@talktalk.net> (Sharon Kimble's message of "Wed, 23 Apr 2014 01:14:14 +0100")
On Wednesday, 23 Apr 2014 at 01:14, Sharon Kimble wrote:
> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
>> On Sunday, 20 Apr 2014 at 12:01, Sharon Kimble wrote:
>>
>> [...]
>>
>>> Unfortunately mine isn't working like that, you get the prompt, and a
>>> "double-n" just dumps you back at the "Group" message buffer, where you have
>>> to manually choose the next group to be read.
>>
>> What is "n" bound to? I.e. what does C-h c n tell you? In my case,
>> it's bound to gnus-summary-next-unread-article.
> Thanks for this, didn't see it until just now.
>
> I've just checked and its bound to "n runs the command self-insert-command",
> which is obviously why 'n' isn't working like it should. How then do I change
> it?
What buffer were you in when you checked? self-insert-command makes
sense for any editing buffer but not for gnus summary or article
buffers.
--
: Eric S Fraga, GnuPG: 0xFFFCF67D
: in Emacs 24.4.50.2 + Ma Gnus v0.10 + evil evil-git-d4ffce0
: BBDB version 3.1.1 (2014-04-12 21:49:18 -0500)
next prev parent reply other threads:[~2014-04-23 11:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87bnvxt1te.fsf@talktalk.net>
[not found] ` <8738h8q0e3.fsf@motoko.kusanagi>
[not found] ` <87y4z0l0xi.fsf@talktalk.net>
2014-04-21 11:51 ` Eric S Fraga
2014-04-23 0:14 ` Sharon Kimble
2014-04-23 11:21 ` Eric S Fraga [this message]
2014-04-23 14:47 ` Sharon Kimble
2014-04-23 15:12 ` Adam Sjøgren
2014-04-23 18:17 ` Sharon Kimble
2014-04-23 19:03 ` Adam Sjøgren
2014-04-23 21:39 ` Sharon Kimble
2014-04-23 23:04 ` Eric Abrahamsen
2014-04-23 23:15 ` Sharon Kimble
2014-04-23 23:28 ` Sharon Kimble
2014-04-24 15:53 ` Adam Sjøgren
2014-04-25 2:56 ` Eric Abrahamsen
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=87y4ywfg0c.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).