From: Jim Porter <jporterbugs@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>,
Duncan Greatwood <dgreatwood@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, dgbulk@gmail.com, 72450@debbugs.gnu.org
Subject: bug#72450: 29.1; Tramp Failed to Parse OS Name and Version for Windows 11
Date: Thu, 8 Aug 2024 11:28:41 -0700 [thread overview]
Message-ID: <95069f51-923e-657c-ead4-ee20c634fb65@gmail.com> (raw)
In-Reply-To: <874j7zpe62.fsf@gmx.de>
On 8/5/2024 1:27 AM, Michael Albinus via Bug reports for GNU Emacs, the
Swiss army knife of text editors wrote:
> Duncan Greatwood <dgreatwood@gmail.com> writes:
>
>> Hi Michael and Eli -
>
> Hi Duncan,
>
>> sh-5.2$ uname --version
>> uname (GNU coreutils) 8.32
>> Copyright (C) 2020 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later
>> <https://gnu.org/licenses/gpl.html>.
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.
>>
>> Written by David MacKenzie.
>> sh-5.2$
>>
>> If I may, the extra characters in the emacs error message might not
>> come from the uname on windows - that uname seems to work OK on the
>> windows side at least - it could be a misparsing in emacs (or even an
>> mistake gathering the error message, I suppose).
>
> I also don't believe it comes from uname itself. '[17;120H’' looks
> rather like an escape code sequence, perhaps emitted from the underlying
> shell. Something like cursor position, window setting, whatever. A
> search didn't gave me a clue what's this.
>
> After connecting the remote host via ssh, Tramp sends as very first
> command something like
>
> --8<---------------cut here---------------start------------->8---
> # exec env TERM='dumb' INSIDE_EMACS='31.0.50,tramp:2.8.0-pre' ENV='' HISTFILE=~/.tramp_history PROMPT_COMMAND='' PS1=///245adade605348c086dac6d8f612435c\#\$ PS2='' PS3='' /bin/sh -i
> --8<---------------cut here---------------end--------------->8---
>
> Note the TERM='dumb' setting, which ought to suppress such code
> sequences.
>
> Somehow, this doesn't seem to work as expected in your case. Perhaps due
> to calling /bin/sh. See below for debugging instructions.
Regarding the unusual cursor-positioning ANSI sequences, I may know what
this is, since I encountered something similar before:
<https://lists.gnu.org/archive/html/tramp-devel/2021-04/msg00024.html>.
This is apparently just another one of those sharp corners on MS-Windows
that we have to deal with for the sake of backwards compatibility
(nice), but that there's no clear way to opt out of (not so nice):
<https://github.com/PowerShell/Win32-OpenSSH/issues/1738>.
>> From an emacs perspective, it seems a shame not to be able to use ssh,
>> given that modern Windows commonly supports ssh and provides a bash
>> shell. Depending on your own available bandwidth etc. of course.
>
> That is NOT a shame. MS Windows is a non-free operation system,
> therefore it isn't a primary target for Emacs development.
>
> And it doesn't seem to be important. I'm working for Tramp for more than
> 20 years. During this time, nobody has contributed anything for the sake
> of MS Windows. And I don't use MS Windows myself; if possible, I fix
> things, that's it.
Well, I've tried to help make Tramp work a bit better on MS-Windows (my
first Emacs patch was to fix Tramp hostname completion on MS-Windows
;)), but this bug is the one where I finally gave up: there's a point
where trying to fix Microsoft's mistakes just becomes too time-consuming
and bothersome, so I focused my energies elsewhere.
As it's been a few years since I looked at this last, the residual
irritation has certainly subsided so I wouldn't mind trying to help out
in some way, but I'm not sure I have the patience to come up with a
patch for this myself.
next prev parent reply other threads:[~2024-08-08 18:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-03 19:54 bug#72450: 29.1; Tramp Failed to Parse OS Name and Version for Windows 11 Duncan Greatwood
2024-08-04 4:41 ` Eli Zaretskii
2024-08-04 8:28 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-04 9:15 ` Eli Zaretskii
2024-08-04 10:37 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-04 10:45 ` Eli Zaretskii
2024-08-04 10:56 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-04 11:01 ` Eli Zaretskii
2024-08-05 3:39 ` Duncan Greatwood
2024-08-05 8:27 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <mvmcymnfjcc.fsf@suse.de>
2024-08-05 11:56 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-05 22:14 ` Duncan Greatwood
2024-08-06 7:40 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-07 21:46 ` Duncan Greatwood
2024-08-08 5:20 ` Eli Zaretskii
2024-08-08 11:06 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-08 11:11 ` Eli Zaretskii
2024-08-08 11:18 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-08 11:11 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-08 18:28 ` Jim Porter [this message]
2024-08-08 19:03 ` Duncan Greatwood
2024-08-10 10:34 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=95069f51-923e-657c-ead4-ee20c634fb65@gmail.com \
--to=jporterbugs@gmail.com \
--cc=72450@debbugs.gnu.org \
--cc=dgbulk@gmail.com \
--cc=dgreatwood@gmail.com \
--cc=eliz@gnu.org \
--cc=michael.albinus@gmx.de \
/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.