From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Colin Williams <lackita@gmail.com>,
"4004@emacsbugs.donarmstrong.com"
<4004@emacsbugs.donarmstrong.com>,
emacs-devel@gnu.org
Subject: bug#4004: filename completion
Date: Mon, 10 Aug 2009 15:53:38 -0400 [thread overview]
Message-ID: <jwvfxbzla87.fsf-monnier+emacsbugreports__40944.043317768$1249934862$gmane$org@gnu.org> (raw)
In-Reply-To: <nqprb7vnhr.fsf@alcatel-lucent.de> (Michael Albinus's message of "Fri, 07 Aug 2009 14:04:32 +0200")
> There was a discussion about some years ago, when I did add Tramp's
> autoloads. People were annoyed, that even after typing something like
> "/a" in the minibuffer, Tramp was already loaded, which raised some
> delays. So it was suggested to make Tramp's autoloading optional. It was
> even requested that this "optionality" should not be something, which
> the user has to disnable herself; users should not be bashed by a new
> feature they are not interested in.
That's beginning to make more sense. But I just tried the following:
emacs -Q
C-x C-f /a TAB :
and then
emacs -Q
M-: (setq partial-completion-mode t)
C-x C-f /a TAB :
and I don't see any difference (Tramp gets loaded when I hit : and no
earlier). Could you show me another example where I can see
the difference, so I can better understand the tradeoffs?
Stefan
next prev parent reply other threads:[~2009-08-10 19:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <nqvdl5e1vm.fsf@alcatel-lucent.de>
2009-08-01 16:36 ` bug#4004: filename completion Colin Williams
2009-08-03 3:13 ` Michael Albinus
2009-08-03 18:37 ` Stefan Monnier
2009-08-03 18:46 ` Michael Albinus
2009-08-06 18:37 ` Stefan Monnier
2009-08-07 12:04 ` Michael Albinus
[not found] ` <nqprb7vnhr.fsf@alcatel-lucent.de>
2009-08-10 19:53 ` Stefan Monnier [this message]
[not found] ` <jwvfxbzla87.fsf-monnier+emacsbugreports@gnu.org>
2009-08-10 20:06 ` Lennart Borgman
2009-08-03 8:40 ` bug#4004: marked as done (filename completion) Emacs bug Tracking System
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='jwvfxbzla87.fsf-monnier+emacsbugreports__40944.043317768$1249934862$gmane$org@gnu.org' \
--to=monnier@iro.umontreal.ca \
--cc=4004@emacsbugs.donarmstrong.com \
--cc=emacs-devel@gnu.org \
--cc=lackita@gmail.com \
--cc=michael.albinus@gmx.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.
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).