all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: bug-gnu-emacs@gnu.org, Thierry Volpiatto <thierry.volpiatto@gmail.com>
Subject: bug#5840: 24.0.50; wrong tramp-file-name-regexp
Date: Mon, 12 Apr 2010 21:08:53 +0200	[thread overview]
Message-ID: <87ochoebei.fsf@gmx.de> (raw)
In-Reply-To: <jwv633wtu23.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 12 Apr 2010 14:20:47 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> so it'd be OK.  Two issues, tho:
> 1- first, I'd like to know why Tramp doesn't just signal an error,
>    rather than mess with windows and stuff.

As I said, Tramp's syntax is ambigous. It tries to expand "/sudo:",
which is a valid remote file name. Due to the syntax ambiguity, Tramp
does not understand, that "sudo" is not a hostname in this case, and it
fails with an error. What you see is the usual Tramp behaviour in case
of an error, where it tries to give you some more information in case a
connection does not work.

The amount of information can be reduced by lowering `tramp-verbose'.

> 2- if we have to go this route it'll have to use a name that's not
>    specific to tramp.  Maybe `completion-only' or something like that.

D'accord. I had always a bad feeling spreading Tramp internal names to
the outside; when we have introduced that variable back in 2005 and
2007, Emacs was in a kind of feature freeze (IIRC), so I didn't ask for
such a variable.

`completion-*' symbols are spread over several *.el files. Where shall
`completion-only' belong to? minibuffer.el?

> -- Stefan

Best regards, Michael.







  reply	other threads:[~2010-04-12 19:08 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 [this message]
2010-04-12 20:51             ` Stefan Monnier
2010-04-13  4:32               ` Michael Albinus
2010-04-13  6:25                 ` Thierry Volpiatto
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ochoebei.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=thierry.volpiatto@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.