GNU bug report logs - #23186
25.0.92; Tramp: Windows does not always set COMSPEC, tramp blows up in a string-match

Previous Next

Full log

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

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Jerry Asher <ja2038 <at> gmail.com>, 23186 <at> debbugs.gnu.org
Subject: Re: bug#23186: 25.0.92;
 Tramp: Windows does not always set COMSPEC, tramp blows up in a
 string-match
Date: Sat, 02 Apr 2016 21:37:51 +0200

Eli Zaretskii <eliz <at> gnu.org> writes:

>> Regardless, I would say the assumption that COMSPEC is always set
>> and so therefore if it fails it is okay to
>> assign nil to tramp-encoding-shell knowing that later on it will be
>> in a string-match is problematic in and of
>> itself. 
>
> Tramp is designed to work with Emacs as released by the Emacs
> development team.  That Emacs doesn't have this problem.  I think it
> would be unreasonable for anyone to expect the Tramp maintainers to
> cater to arbitrary changes in the Emacs code or in how it is
> configured on Windows, let alone if you poke some addresses in the PE
> headers of the produced binary.

The Tramp maintainers could check, whether COMSPEC is set, and raise a
verbose warning in case it isn't. Refusing further work.

Shall I commit this to the emacs-25 branch, or to master?

Best regards, Michael.

Previous Next

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