From: Harry Putnam <reader@newsguy.com>
Subject: Re: What has happened to my echo area?
Date: Tue, 23 Apr 2002 09:07:56 -0700 [thread overview]
Message-ID: <m13cxmgzz7.fsf@reader.newsguy.com> (raw)
In-Reply-To: <m3k7qye864.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Tue, 23 Apr 2002 11:38:53 -0400")
prj@po.cwru.edu (Paul Jarc) writes:
> Harry Putnam <reader@newsguy.com> wrote:
>> I've been noticing lately that things that used to be echoed in the echo
>> area no longer do so. A few exampes:
>>
>> Pressing C-u before entering a group
>> Pressing NUMBER before entering a group
>> Pressing C-u g in summary buffer to view a raw article
>
> These still echo for me, but only if there is a delay between
> keystrokes. After the delay, all keystrokes so far are echoed,
> further keystrokes are echoed as soon as they are typed, and the
> entire key sequence stays in the echo area until the next keystroke.
> If there is no delay, nothing gets echoed.
What on earth might have derailed it for me?
For example: In this composition buffer, pressing C-h <waiting a few
seconds> nothing shows in the echo area. Finish by pressing `m' so
I've pressed C-h m and the expected buffer pops up but nothing ever
showed up in echo area.
I can't think of recent local changes that might cause this but I really
have no idea of where to start looking. I can say that in another
emacs instance running next to this one that happens to have a perl script
in it, pressing C-h there shows C-h within a second in echo area.
So seems it may be related to gnus or to message-mode.
Both instances are started from the same init files.
next prev parent reply other threads:[~2002-04-23 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-23 15:33 Harry Putnam
2002-04-23 15:38 ` Paul Jarc
2002-04-23 16:07 ` Harry Putnam [this message]
2002-04-23 16:33 ` Karl Kleinpaste
2002-04-23 16:34 ` Kai Großjohann
2002-04-23 16:55 ` Harry Putnam
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=m13cxmgzz7.fsf@reader.newsguy.com \
--to=reader@newsguy.com \
/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).