From: Simon Josefsson <jas@extundo.com>
Subject: Re: Improve G m to make it more user friendly?
Date: Sat, 17 Jul 2004 19:26:09 +0200 [thread overview]
Message-ID: <iluvfgm1r66.fsf@latte.josefsson.org> (raw)
In-Reply-To: <86iscmoddn.fsf@rumba.de.uu.net>
Kai Grossjohann <kai@emptydomain.de> writes:
> Simon Josefsson <jas@extundo.com> writes:
>
>> How about making it just G m nnimap+bar:INBOX.foo RET, making sure the
>> auto completion is smart enough to notice what field the user want to
>> complete?
>
> That would be great!
Yup. How about what's in CVS now? I didn't really test it.
next prev parent reply other threads:[~2004-07-17 17:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 13:40 Kai Grossjohann
2004-07-14 18:31 ` Simon Josefsson
2004-07-17 15:35 ` Kai Grossjohann
2004-07-17 17:26 ` Simon Josefsson [this message]
2004-07-18 14:50 ` Marcus Frings
2004-07-18 22:54 ` Simon Josefsson
2004-07-19 11:34 ` Marcus Frings
2004-07-20 12:37 ` Katsumi Yamaoka
2004-07-25 13:20 ` Harry Putnam
2004-07-26 16:37 ` Simon Josefsson
2004-07-26 18:21 ` Harry Putnam
2004-07-18 14:48 ` Marcus Frings
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=iluvfgm1r66.fsf@latte.josefsson.org \
--to=jas@extundo.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).