From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: A couple of keys are behaving differently
Date: Thu, 02 Jan 2003 03:04:31 +0100 [thread overview]
Message-ID: <m3znqkwbm8.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <microsoft-free.x4pu2loe4h.fsf@eicq.dnsalias.org>
Steve Youngs <youngs@xemacs.org> writes:
> When hitting 'n' on the last article in the summary buffer it no
> longer tells me which group (and number of articles) it's going to
> next.
How strange. It looks like `read-event' has started to output the
current prefix key while reading.
I've now supplied a prompt argument to `read-event', and the message
is now back.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2003-01-02 2:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-03 15:38 Steve Youngs
2003-01-02 2:04 ` Lars Magne Ingebrigtsen [this message]
2002-03-03 15:38 Steve Youngs
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=m3znqkwbm8.fsf@quimbies.gnus.org \
--to=larsi@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).