all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
Cc: 26387@debbugs.gnu.org
Subject: bug#26387: Issues in IDO/Tramp interaction
Date: Fri, 07 Apr 2017 12:11:37 +0200	[thread overview]
Message-ID: <87h920le7a.fsf@detlef> (raw)
In-Reply-To: <d341ce57-9fdc-c5ad-7c82-3f1e4083c5ab@gmail.com> ("Clément Pit-Claudel"'s message of "Thu, 6 Apr 2017 16:28:03 -0400")

Clément Pit-Claudel <cpitclaudel@gmail.com> writes:

> Hi bug-gnu-emacs,

Hi Clément,

> (Not sure if this should go here or tramp-devel)

Tramp maintainers read also this ML :-)

> There are a few compatibility issues between IDO and Tramp:
>
> 1. In IDO, '~' is always interpreted as a local path.  That is, if
> after enabling IDO mode I type C-x C-f /sshx:user@host:~/, then IDO
> immediately removes the /sshx:user@host: prefix.

I cannot say too much about, looks to me like an ido issue. 

> 2. Running M-x shell in a buffer editing a remote file results in a
> prompt saying "Remote shell path: /sshx:user@host:/home/user//bin/bash
> (not found)".  The coorrect prompt would be
> "/sshx:user@host:/bin/bash".

I get "/sudo:root@host:/root//usr/bin/tcsh [Matched]". Does /bin/bash
exist on your remote machine?

And btw, I recommend you to use connection-local variables in order to
avoid this question. See the example in (info "(tramp) Remote processes")

> Cheers,
> Clément.

Best regards, Michael.





  reply	other threads:[~2017-04-07 10:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06 20:28 bug#26387: Issues in IDO/Tramp interaction Clément Pit-Claudel
2017-04-07 10:11 ` Michael Albinus [this message]
2017-04-10  7:09   ` Clément Pit-Claudel
2017-04-10  7:35     ` Michael Albinus
2017-04-10 15:12       ` Clément Pit-Claudel

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=87h920le7a.fsf@detlef \
    --to=michael.albinus@gmx.de \
    --cc=26387@debbugs.gnu.org \
    --cc=cpitclaudel@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.