all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Dima Kogan <dima@secretsauce.net>
Cc: 28119-done@debbugs.gnu.org
Subject: bug#28119: 26.0.50; TRAMP: Can't open "/sudo::/tmp" after (tramp-change-syntax 'simplified)
Date: Thu, 17 Aug 2017 09:21:08 +0200	[thread overview]
Message-ID: <871soa4q3f.fsf@detlef> (raw)
In-Reply-To: <87a82yivwq.fsf@scrawny> (Dima Kogan's message of "Wed, 16 Aug 2017 22:51:49 -0700")

Dima Kogan <dima@secretsauce.net> writes:

> Hi.

Hi Dima,

> I'm running a bleeding-edge build of emacs from git. I turned on
> what I thought was the old-style TRAMP syntax by evaluating
>
>   (tramp-change-syntax 'simplified)
>
> This gives me the old syntax for ssh, but other modes don't work
> anymore. For instance, trying to open /sudo::/whatever now tries to
> contact an ssh server named "sudo". Is this expected? Is the 'simplified
> syntax not an old-style compability syntax?

`simplified' is not an old-style compatibility. The "old-style" syntax,
allowing the method name to be optional, has been thrown away
completely. You use now either "/method:user@host:" as the changed
default syntaxw (user and host are optional), or "/user@host:" as the
symplified syntax (user being optional). Simplified syntax looks similar
to the old ange-ftp syntax.

With the simplified syntax, you declare your default method via
`tramp-default-method-alist' or `tramp-default-method'.

I'm marking this ticket as notabug and closed, but of course we could
continue to discuss how to optimize your settings.

Best regards, Michael.





      reply	other threads:[~2017-08-17  7:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-17  5:51 bug#28119: 26.0.50; TRAMP: Can't open "/sudo::/tmp" after (tramp-change-syntax 'simplified) Dima Kogan
2017-08-17  7:21 ` Michael Albinus [this message]

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=871soa4q3f.fsf@detlef \
    --to=michael.albinus@gmx.de \
    --cc=28119-done@debbugs.gnu.org \
    --cc=dima@secretsauce.net \
    /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.