From: "Drew Adams" <drew.adams@oracle.com>
To: "Sebastian Tennant" <sebyte@smolny.plus.com>, <help-gnu-emacs@gnu.org>
Subject: RE: Configure SPACE as file auto-complete character
Date: Mon, 17 Dec 2007 14:03:50 -0800 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICAEALECAA.drew.adams@oracle.com> (raw)
In-Reply-To: <87lk7t10zk.fsf@moley.moleskin.org>
> Interesting... I've had the following line in my ~/.emacs for quite a
> while for precisely this reason:
>
> ;;; disable 'SPC' completion in minibuffer
> (substitute-key-definition 'minibuffer-complete-word
> 'self-insert-command minibuffer-local-completion-map)
>
> However, I believe my substitution disables auto-completion across the
> board, not just file name auto-completion.
And that's a good thing, IMO. I doubt that you regret it.
Completion using `completing-read' is general; there is nothing that
suggests that it should be mainly for text that doesn't contain spaces. Why
does Emacs limit space self-insertion to file-name completion?
Thank goodness for at least that change. It was due at least in part to the
widespread use of MS Windows (and also to the fact that word-by-word
completion is not so useful).
FWIW - In Icicles, each of these characters self-inserts in the minibuffer:
`?', `C-j' (newline), and `SPC' - regardless of the input type. You can
still do word-by-word completion, using `M-SPC' (configurable), but I'm sure
that any use of word-by-word completion is rare.
next prev parent reply other threads:[~2007-12-17 22:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 2:46 Configure SPACE as file auto-complete character Bruza
2007-12-17 9:48 ` Jason Rumney
2007-12-17 20:28 ` Eli Zaretskii
2007-12-17 21:10 ` Sebastian Tennant
2007-12-17 22:03 ` Drew Adams [this message]
2007-12-18 15:38 ` rob wahoo
2007-12-21 23:16 ` Bruza
[not found] <mailman.5130.1197929124.18990.help-gnu-emacs@gnu.org>
2007-12-18 5:13 ` Bruza
2007-12-18 6:52 ` Klaus Zeitler
2007-12-18 14:17 ` Sebastian Tennant
2007-12-18 15:30 ` Drew Adams
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=DNEMKBNJBGPAOPIJOOICAEALECAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=sebyte@smolny.plus.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 read-only IMAP folder(s) and NNTP newsgroup(s).