From: "Ken Manheimer" <ken.manheimer@gmail.com>
Subject: Fwd: Prepend an indicator to the minibuffer prompt to show you can use completion
Date: Mon, 14 Aug 2006 13:24:12 -0400 [thread overview]
Message-ID: <2cd46e7f0608141024h2bed4a09m94233546df865dbf@mail.gmail.com> (raw)
In-Reply-To: <2cd46e7f0608141023r3ecd44fdl48287a2aa3a33068@mail.gmail.com>
[whoops - sent a separate copy directly to drew, meant to cc the list.]
On 8/13/06, Drew Adams <drew.adams@oracle.com> wrote:
> Minor feature suggestion, for after the release:
>
> Prepend a one-character indicator, with a face that stands out, to the
> minibuffer prompt, whenever completion is possible.
> [...]
> Knowing whether completion is available can change the way you interact with
> Emacs. Not knowing it is available can mean that you miss out on a quick way
> of inputting something.
i like this idea. i have a few modifications.
first, i would prefer to use a new indicator in the fringe, when the
fringe is present - seems like this would be a nice use of that real
estate, more suitable than precious minibuffer content space. the new
cue would display with the fringe top-of-buffer signal, when people
use that, but that's generally redundant in the minibuffer, since it
always has a prompt on the first line, and usually contains one or
just a few lines.
second, you get many of the benefits you seek, and more, with
something like icomplete. with icomplete, on the third character you
get a concise indication of the completion prospects, not just that
completion is available. a fringe indicator would not conflict,
however, and would still be nice, though less necessary.
> An additional subtlety can help a little more: I prepend a different
> character (`=') and highlight it in a different color, whenever completion
> requires a match.
with icomplete you get different braces around the completion
prospects depending on whether the match is required or optional.
i think that having the option for an indicator in the fringe, whether
or not you use something like icomplete, would be good.
--
ken
ken.manheimer@gmail.com
http://myriadicity.net
--
ken
ken.manheimer@gmail.com
http://myriadicity.net
next prev parent reply other threads:[~2006-08-14 17:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-13 19:38 Prepend an indicator to the minibuffer prompt to show you can use completion Drew Adams
[not found] ` <2cd46e7f0608141023r3ecd44fdl48287a2aa3a33068@mail.gmail.com>
2006-08-14 17:24 ` Ken Manheimer [this message]
2006-08-14 18:47 ` Prepend an indicator to the minibuffer prompt to show you canuse completion Drew Adams
2006-08-17 19:36 ` Kevin Rodgers
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2cd46e7f0608141024h2bed4a09m94233546df865dbf@mail.gmail.com \
--to=ken.manheimer@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).