unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: emacs-devel@gnu.org, help-gnu-emacs@gnu.org, tramp-devel@gnu.org
Subject: Modified remote file name syntax
Date: Mon, 13 Mar 2017 18:20:37 +0100	[thread overview]
Message-ID: <8737ehayai.fsf@detlef> (raw)

Hi,

today I've committed a patch, which changes the remote file name syntax
in Emacs. The "method" part, optional until now, becomes
mandatory. Valid remote file names are now

/method:host:/path/to/file
/method:user@host:/path/to/file

A new method, "-", has been added which is a marker for the default
method as known so far.

The reason is, that all the time there have been problems in Tramp due
to syntactic ambiguities. A remote file name "/foo:" has not been
distinct; "foo" could be either a method or a host name. This has
resulted in permanent problems during file name completion.

The changes will be visible with the next releases of Tramp 2.3.2 and
Emacs 26.1.

Best regards, Michael.

                 reply	other threads:[~2017-03-13 17:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=8737ehayai.fsf@detlef \
    --to=michael.albinus@gmx.de \
    --cc=emacs-devel@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=tramp-devel@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.
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).