From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Slight `B m' history misbehavior
Date: Sat, 06 Oct 2001 21:26:44 +0200 [thread overview]
Message-ID: <vafwv28bmdn.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3r8sgd806.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Sat, 06 Oct 2001 12:53:55 -0400")
prj@po.cwru.edu (Paul Jarc) writes:
> I'd say the minibuffer contents should not be bogus. Let it contain
> the default or be empty.
The current contents are nicer, because you just have to add the group
name rather than also delete the old group name.
Otherwise we would have to come up with something like the
double-slash trick for filenames, only for group names.
kai
--
Linux provides a nice `poweroff' command, but where is `poweron'?
prev parent reply other threads:[~2001-10-06 19:26 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
2001-10-06 19:26 ` Kai Großjohann [this message]
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=vafwv28bmdn.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).