|
From: | Michael Albinus |
Subject: | bug#23186: closed (Re: bug#23186: 25.0.92; Tramp: Windows does not always set COMSPEC, tramp blows up in a string-match) |
Date: | Sun, 03 Apr 2016 09:15:11 +0200 |
User-agent: | Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) |
Eli Zaretskii <eliz@gnu.org> writes: Hi Jerry, >> What is the full contents of the environment of the Emacs process when >> you run that zapped binary? > > I'm still waiting for the answer to that question. It's important, > for the reasons explained below. I second Eli. First of all we must understand why COMSPEC isn't set in your case. Just applying a workaround doesn't suffice at first glance, it could be that there is amuch more serious problem behind. Tramp could be just the first victim entering this problem. Who knows. >> WHAT DO YOU THE MAINTAINER PROPOSE as a solution? Investigate. As Eli proposed. And for the upcoming Emacs 25.1, we just report the error. We cannot do anything else so late in the pretest. Best regards, Michael.
[Prev in Thread] | Current Thread | [Next in Thread] |