From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 'Juri Linkov' <juri@jurta.org>,
'Chong Yidong' <cyd@stupidchicken.com>,
'paul r' <paul.r.ml@gmail.com>,
'emacs- devel' <emacs-devel@gnu.org>
Subject: Re: Usability suggestion : completion for M-:
Date: Sun, 16 Mar 2008 13:27:09 +0100 [thread overview]
Message-ID: <47DD121D.60000@gmail.com> (raw)
In-Reply-To: <000601c8873d$7625c240$0600a8c0@us.oracle.com>
Drew Adams wrote:
> I said, "M-TAB or ESC TAB".
I noticed, but I find ESC TAB quite a bit inconvenient for such a common
operation as completion.
>> - TAB is rather commonly used for completion (for example
>> when reading file names in Emacs, in shells, hacks to use
>> TAB for completions in Emacs are seen as positive by some Emacs users)
>
> Did you read what I wrote? TAB can be used for some other, better completion
> in M-: than symbol completion - completion that would be consistent with
> other minibuffer completion (complete the whole input, then RET to enter).
Sorry, I missed that part.
Do you mean adding closing parenthesis? Then it could be combined I believe.
next prev parent reply other threads:[~2008-03-16 12:27 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 17:30 Usability suggestion : completion for M-: paul r
2008-03-13 18:04 ` Lennart Borgman (gmail)
2008-03-13 21:16 ` Drew Adams
2008-03-13 21:32 ` paul r
2008-03-13 21:45 ` Lennart Borgman (gmail)
2008-03-13 23:32 ` Chong Yidong
2008-03-13 23:49 ` Drew Adams
2008-03-21 5:21 ` Drew Adams
2008-03-14 8:52 ` paul r
2008-03-15 21:36 ` Juri Linkov
2008-03-15 23:35 ` Drew Adams
2008-03-15 23:43 ` Lennart Borgman (gmail)
2008-03-16 8:12 ` Drew Adams
2008-03-16 11:00 ` paul r
2008-03-16 11:21 ` Ralf Angeli
2008-03-16 16:52 ` Drew Adams
2008-03-16 12:27 ` Lennart Borgman (gmail) [this message]
2008-03-16 16:50 ` Drew Adams
2008-03-16 0:17 ` Juri Linkov
2008-03-16 8:11 ` Drew Adams
2008-03-16 10:48 ` Andreas Schwab
2008-03-16 12:22 ` Lennart Borgman (gmail)
2008-03-16 13:36 ` Andreas Schwab
2008-03-16 10:56 ` paul r
2008-03-16 16:49 ` Drew Adams
2008-03-16 18:42 ` paul r
2008-03-16 19:56 ` Bastien
2008-03-16 20:22 ` David De La Harpe Golden
2008-03-17 2:52 ` Stefan Monnier
2008-03-17 4:07 ` Mike Mattie
2008-03-17 13:32 ` Stefan Monnier
2008-03-17 9:32 ` paul r
2008-03-17 19:16 ` Richard Stallman
2008-03-18 9:19 ` paul r
2008-03-19 2:53 ` Richard Stallman
2008-03-19 16:28 ` Stefan Monnier
2008-03-19 18:16 ` paul r
2008-03-19 19:25 ` Andreas Schwab
2008-03-16 18:49 ` paul r
2008-03-16 12:31 ` Lennart Borgman (gmail)
2008-03-16 16:50 ` Drew Adams
2008-03-16 20:06 ` Bastien Guerry
2008-03-22 21:14 ` Chong Yidong
2008-03-23 2:30 ` Juri Linkov
2008-03-23 5:54 ` Drew Adams
2008-04-09 20:42 ` Paul R
2008-04-09 21:20 ` Drew Adams
2008-04-10 23:12 ` Juri Linkov
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=47DD121D.60000@gmail.com \
--to=lennart.borgman@gmail.com \
--cc=cyd@stupidchicken.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=paul.r.ml@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).