unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ed Avis <ed.avis@qmaw.com>
Cc: larsi@gnus.org, 45042@debbugs.gnu.org
Subject: bug#45042: 27.1; emacs -nw on Windows does not always update cursor position on screen
Date: Mon, 25 Jan 2021 17:32:30 +0200	[thread overview]
Message-ID: <83eei92fsh.fsf@gnu.org> (raw)
In-Reply-To: <PH0PR11MB48871260CAF148A1E7D5F4029DBD9@PH0PR11MB4887.namprd11.prod.outlook.com> (message from Ed Avis on Mon, 25 Jan 2021 08:00:00 +0000)

> From: Ed Avis <ed.avis@qmaw.com>
> CC: "larsi@gnus.org" <larsi@gnus.org>,
>  "45042@debbugs.gnu.org"<45042@debbugs.gnu.org>
> Date: Mon, 25 Jan 2021 08:00:00 +0000
> 
> The problem with the cursor movement not updating doesn't just happen under Alacritty.  I can also
> reproduce it using an ssh server on Windows, by sshing to the machine and running emacs -nw.  The ssh
> client can be PuTTY or the Windows port of OpenSSH running in the Windows command prompt.  Unsetting
> TERM does not appear to make a difference in any of these cases.

PuTTY emulates a Unix terminal with terminfo database, and thus
expects the program to send escape sequences to move the cursor.  If
the OpenSSH client used by Windows does the same, then it means these
two emulators aren't currently supported by Emacs on Windows, because
Emacs assumes a native Windows console.

Patches to add support for curses-like escape sequences are welcome.





  reply	other threads:[~2021-01-25 15:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04 18:53 bug#45042: 27.1; emacs -nw on Windows does not always update cursor position on screen Ed Avis
2020-12-05  7:40 ` Eli Zaretskii
2021-01-23 23:16   ` Lars Ingebrigtsen
2021-01-24  7:22     ` Ed Avis
2021-01-24 14:46       ` Eli Zaretskii
2021-01-25  8:00         ` Ed Avis
2021-01-25 15:32           ` Eli Zaretskii [this message]
2021-01-26  7:21             ` Ed Avis
2021-01-26 15:07               ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83eei92fsh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=45042@debbugs.gnu.org \
    --cc=ed.avis@qmaw.com \
    --cc=larsi@gnus.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).