From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Drew Adams <drew.adams@oracle.com>, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r108646: * minibuffer.el(read-file-name-default): Bind `non-essential' to `t'.
Date: Tue, 19 Jun 2012 12:29:02 -0400 [thread overview]
Message-ID: <jwvwr33l1xi.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87hau7e86t.fsf@gmx.de> (Michael Albinus's message of "Tue, 19 Jun 2012 15:35:06 +0200")
>> 1. I'm on Windows. This is missing at the beginning of the recipe:
>>
>> M-x load-file c:/path/to/cygwin-mount.el
>> M-x load-file c:/path/to/setup-cygwin.el
> Nothing I could reproduce, I'm not on Windows.
>> 2. And you left this out, Michael:
>>
>> (setq tramp-default-method "ftp")
>>
>> 3. And the last step is this (no ssh):
>>
>> C-x C-f /foobar.baztoto.com:
>> ^ Tramp asks for the password
>>
> OK, again on Ubuntu:
> src/emacs -Q
> (require 'icomplete)
> (setq icomplete-with-completion-tables
> (append icomplete-with-completion-tables
> '(read-file-name-internal)))
> (icomplete-mode 1)
> (setq tramp-default-method "ftp")
> C-x C-f /foobar.baztoto.com:
> ^ no problem so far
> <TAB>
> ^ nothing happens
> /
> ^ I get an error:
> Error in post-command-hook (#[nil \300\301!\207 [run-hooks
> icomplete-post-command-hook] 2]): (error "Command attempted to use
> minibuffer while in minibuffer")
> But that's another story. Problem in icomplete?
That "Command attempted to use minibuffer while in minibuffer" is
because icomplete triggered a Tramp connection which tried to use
the minibuffer to get a password.
So if you add (setq enable-recursive-minibuffers t) to the above recipe
you can reproduce the problem.
I don't think Tramp should attempt a connection in that case since
(according to M-x trace-function RET icomplete-completions) the password
prompt happens during the call to icomplete-completions which binds
non-essential to t.
Stefan
next prev parent reply other threads:[~2012-06-19 16:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1SgKyP-0002jR-81@vcs.savannah.gnu.org>
2012-06-18 2:15 ` [Emacs-diffs] /srv/bzr/emacs/trunk r108646: * minibuffer.el (read-file-name-default): Bind `non-essential' to `t' Stefan Monnier
2012-06-18 9:00 ` Michael Albinus
2012-06-18 14:03 ` Stefan Monnier
2012-06-18 14:58 ` [Emacs-diffs] /srv/bzr/emacs/trunk r108646: * minibuffer.el(read-file-name-default): " Drew Adams
2012-06-18 15:59 ` Stefan Monnier
2012-06-18 19:58 ` Drew Adams
2012-06-18 21:20 ` Stefan Monnier
2012-06-19 12:36 ` Michael Albinus
2012-06-19 13:16 ` Drew Adams
2012-06-19 13:35 ` Michael Albinus
2012-06-19 16:29 ` Stefan Monnier [this message]
2012-06-19 19:03 ` Michael Albinus
2012-06-20 6:57 ` Michael Albinus
2012-06-20 13:29 ` Drew Adams
2012-06-18 16:47 ` [Emacs-diffs] /srv/bzr/emacs/trunk r108646: * minibuffer.el (read-file-name-default): " Michael Albinus
2012-06-18 20:35 ` Stefan Monnier
2012-06-18 20:41 ` Michael Albinus
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=jwvwr33l1xi.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--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).