From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: bug-gnu-emacs@gnu.org
Subject: bug#5840: 24.0.50; wrong tramp-file-name-regexp
Date: Tue, 13 Apr 2010 08:25:30 +0200 [thread overview]
Message-ID: <8739yz6f8l.fsf@tux.homenetwork> (raw)
In-Reply-To: <87d3ydw1wr.fsf@tux.homenetwork>
Michael Albinus <michael.albinus@gmx.de> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>> Or maybe it should be provided differently: we could make it so that
>> the top-level exception handler (the one that outputs the message in
>> the minibuffer if an error is not otherwise caught) can be programmed,
>> so Tramp could call `signal' in the normal way and do the messy
>> window-pop-up in the top-level exception handler instead (so it
>> doesn't do it if the error gets caught).
>
> This would be an option, yes. Also for other use cases than this reported one.
>
>> That could save us from a `completion-only' kind of hack.
>
> No. It is not only about catching errors. If, for example, your default
> method is "ftp", expanding "/sudo:" would not result in an error, but in
> the password request for "albinus@sudo" (in my case). This must be
> suppressed as well, so we still need this flag to tell Tramp not to
> expand an incomplete filename.
>
>>> Where shall `completion-only' belong to? minibuffer.el?
>>
>> Yes.
>
> I'll commit it later today.
The patch you sent to me against minibuffer.el was working fine.
However i tried to complete with Emacs build of today
(<2010-04-13 Mar.>)
and even if it complete, i still have the error buffer as soon as i
enter the first ":" (e.g /su::).
With my anything file completion i have no error but i have now to
require tramp.
--
Thierry Volpiatto
Gpg key: http://pgp.mit.edu/
next prev parent reply other threads:[~2010-04-13 6:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 6:06 bug#5840: 24.0.50; wrong tramp-file-name-regexp Thierry Volpiatto
2010-04-11 16:54 ` Michael Albinus
2010-04-11 18:53 ` Stefan Monnier
2010-04-11 20:12 ` Thierry Volpiatto
2010-04-12 5:20 ` Michael Albinus
2010-04-12 6:02 ` Thierry Volpiatto
2010-04-12 4:41 ` Michael Albinus
2010-04-12 15:14 ` Thierry Volpiatto
2010-04-12 18:20 ` Stefan Monnier
2010-04-12 19:08 ` Michael Albinus
2010-04-12 20:51 ` Stefan Monnier
2010-04-13 4:32 ` Michael Albinus
2010-04-13 6:25 ` Thierry Volpiatto [this message]
2010-04-13 12:31 ` Stefan Monnier
2010-04-13 13:09 ` Stefan Monnier
2010-04-13 13:28 ` Michael Albinus
2010-04-14 15:31 ` Stefan Monnier
2010-04-14 22:11 ` Michael Albinus
2010-04-15 5:01 ` Stefan Monnier
2010-04-15 13:06 ` Michael Albinus
2010-04-15 18:59 ` Stefan Monnier
2010-04-15 19:22 ` Stefan Monnier
2010-04-15 22:32 ` Michael Albinus
2010-04-16 0:32 ` Stefan Monnier
2010-04-21 19:52 ` Michael Albinus
2011-11-20 16:15 ` 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=8739yz6f8l.fsf@tux.homenetwork \
--to=thierry.volpiatto@gmail.com \
--cc=bug-gnu-emacs@gnu.org \
/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).