GNU bug report logs - #33791
26.1; Eshell on Windows connecting to GNU/Linux machine using TRAMP and plink: env: ‘c:/home/jordan/test.sh’: No such file or directory

Previous Next

Package: emacs;

Reported by: Jordan Wilson <jordan.t.wilson <at> gmx.com>

Date: Tue, 18 Dec 2018 15:02:01 UTC

Severity: minor

Merged with 24787

Found in versions 25.1, 26.1

Fixed in version 26.2

Done: Michael Albinus <michael.albinus <at> gmx.de>

Bug is archived. No further changes may be made.

Full log


Message #20 received at 33791 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: jordan.t.wilson <at> gmx.com, 33791 <at> debbugs.gnu.org
Subject: Re: bug#33791: 26.1; Eshell on Windows connecting to GNU/Linux
 machine using TRAMP and plink: env: ‘c:/home/jordan/test.sh’: No such file or directory
Date: Sat, 22 Dec 2018 16:36:04 +0200
> From: Michael Albinus <michael.albinus <at> gmx.de>
> Cc: jordan.t.wilson <at> gmx.com,  33791 <at> debbugs.gnu.org
> Date: Sat, 22 Dec 2018 13:35:47 +0100
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> Isn't this bug#24787?
> >
> > Yes, definitely looks like it.  But I don't think the discussion of
> > that bug ended with any conclusions wrt how to fix it, did it?
> 
> No. It is about MS Windows, and it is a minor bug. That's why I didn't
> chime in. Maybe it's now time to have a look on it.

I hope so.  I'm also quite surprised that the problem is specific to
Windows.  If Eshell does handle remote directories in eshell/cd, then
the fact it doesn't work on Windows might be some silly syntax issue,
like some code somewhere expects a directory to begin with a slash or
something.

> (I wish we would have somebody who cares about eshell, regularly)

Seconded.




This bug report was last modified 6 years and 198 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.