unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 13900@debbugs.gnu.org
Subject: bug#13900: 24.3.50; tramp mode for for /su: and /sudo: on localhost
Date: Sat, 09 Mar 2013 12:34:15 +0100	[thread overview]
Message-ID: <87d2v8g62w.fsf@gmx.de> (raw)
In-Reply-To: <jwv8v5x72e1.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 08 Mar 2013 21:10:18 -0500")

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

> BTW, could you try and make TAB on such a file name "expand" to
> "/ssh:sudo:..." so as to clarify what's going on?
> IOW, demote the "/<host>:" syntax such that it is expanded to the
> corresponding "/<method>:<host>:" form as early as possible (and as
> visibly as possible)?

`expand-file-name' does it already:

(expand-file-name "/sudo:/home/jason/somefile")
 => "/scp:sudo:/home/jason/somefile"

So maybe we could add `expand-file-name' somewhere in the minibuffer
completion remote file names? Sorry, I'm not so familiar with pcomplete
and friends.

> Also, if <host> is the name of an existing method, the behavior should
> be to treat it as a method name, rather than a host name (i.e. force
> the user to type "/ssh:sudo:" if she wants to connect to the "sudo"
> host).

I thought of this already a while ago. The major problem might be
"ftp". Old ange-ftp users who are not interested in Tramp at all will
kill me, when they are forced to type "/ftp:ftp:".

>         Stefan

Best regards, Michael.





  reply	other threads:[~2013-03-09 11:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07 23:16 bug#13900: 24.3.50; tramp mode for for /su: and /sudo: on localhost Jason
2013-03-08  7:49 ` Michael Albinus
2013-03-09  2:10   ` Stefan Monnier
2013-03-09 11:34     ` Michael Albinus [this message]
2013-03-09 13:42       ` Stefan Monnier
2013-03-09 15:47         ` Michael Albinus
2013-03-18 13:09           ` 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=87d2v8g62w.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=13900@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).