From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: What has happened to my echo area?
Date: Tue, 23 Apr 2002 18:34:35 +0200 [thread overview]
Message-ID: <vaf1yd6e5lw.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m13cxmgzz7.fsf@reader.newsguy.com> (Harry Putnam's message of "Tue, 23 Apr 2002 09:07:56 -0700")
Harry Putnam <reader@newsguy.com> writes:
> 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.
Do you use BBDB, perchance? Does it help to say (setq bbdb-electric-p nil)?
kai
--
Silence is foo!
next prev parent reply other threads:[~2002-04-23 16:34 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
2002-04-23 16:33 ` Karl Kleinpaste
2002-04-23 16:34 ` Kai Großjohann [this message]
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=vaf1yd6e5lw.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).