bug#26387: Issues in IDO/Tramp interaction

bug#26387: Issues in IDO/Tramp interaction

[Clément Pit-Claudel]

Hi bug-gnu-emacs,

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

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.

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".

Cheers,
Clément.

bug#26387: Issues in IDO/Tramp interaction

[Michael Albinus]

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.

bug#26387: Issues in IDO/Tramp interaction

[Clément Pit-Claudel]

On 2017-04-07 06:11, Michael Albinus wrote:
>> 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?

It does. Ideally, shouldn't it print as "/sudo:root@host:/usr/bin/tcsh" instead of "/sudo:root@host:/root//usr/bin/tcsh" anyway?
Currently, it shows "Shell remote path: /ssh:clement@host:/home/clement//bin/bash [No match]"; everything before "/bin/bash" is highlighted and read-only, and pressing RET doesn't do anything. Instead I need to press C-e to get into edit mode then RET to get "/ssh:clement@host:/bin/bash", and finally I can confirm with RET.

Cheers,
Clément.

bug#26387: Issues in IDO/Tramp interaction

[Michael Albinus]

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

> On 2017-04-07 06:11, Michael Albinus wrote:
>>> 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?
>
> It does. Ideally, shouldn't it print as
> "/sudo:root@host:/usr/bin/tcsh" instead of
> "/sudo:root@host:/root//usr/bin/tcsh" anyway?

Both notations are equivalent. Before being called, the file name passes
`substitute-in-file-name'.

> Currently, it shows "Shell remote path:
> /ssh:clement@host:/home/clement//bin/bash [No match]"; everything
> before "/bin/bash" is highlighted and read-only, and pressing RET
> doesn't do anything.

Only the "/home/clement/" part shall be shown differently.

> Instead I need to press C-e to get into edit mode
> then RET to get "/ssh:clement@host:/bin/bash", and finally I can
> confirm with RET.

I cannot reproduce this locally. Could you, pls, start

emacs -Q -f ido-mode

and check, whether the problem persists?

> Cheers,
> Clément.

Best regards, Michael.

bug#26387: Issues in IDO/Tramp interaction

[Clément Pit-Claudel]

On 2017-04-10 03:35, Michael Albinus wrote:
> I cannot reproduce this locally. Could you, pls, start
> 
> emacs -Q -f ido-mode

You're right, sorry; the following is enough to reproduce it:

  emacs -Q --eval "(setq ido-everywhere t)" -f ido-mode

Clément