From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Slight `B m' history misbehavior
Date: Sat, 06 Oct 2001 12:53:55 -0400 [thread overview]
Message-ID: <m3r8sgd806.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <vafelohkvsx.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Sat, 06 Oct 2001 10:38:22 +0200")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) wrote:
> The prompt tells me that `nnml:a' is the default, so even though the
> initial minibuffer contents are `nnimap:', as before, I just hit RET
> and that works.
...
> Do you agree that after just hitting RET, the (bogus) minibuffer
> contents should not be put in the history?
I'd say the minibuffer contents should not be bogus. Let it contain
the default or be empty.
> How to achieve that?
I can't help there.
paul
next prev parent reply other threads:[~2001-10-06 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-06 8:38 Kai Großjohann
2001-10-06 16:53 ` Paul Jarc [this message]
2001-10-06 19:26 ` Kai Großjohann
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=m3r8sgd806.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/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).