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: Tue, 26 Jan 2021 17:07:25 +0200 [thread overview]
Message-ID: <83h7n320uq.fsf@gnu.org> (raw)
In-Reply-To: <PH0PR11MB48875CF654B5D7DFFDA30E359DBC9@PH0PR11MB4887.namprd11.prod.outlook.com> (message from Ed Avis on Tue, 26 Jan 2021 07:21:27 +0000)
> From: Ed Avis <ed.avis@qmaw.com>
> CC: "larsi@gnus.org" <larsi@gnus.org>,
> "45042@debbugs.gnu.org"<45042@debbugs.gnu.org>
> Date: Tue, 26 Jan 2021 07:21:27 +0000
>
> Thanks for the explanation. So although Emacs uses escape sequences to move the cursor on Unix-like
> platforms, the Windows build uses the native console API. What surprised me was that the cursor position
> does update for up and down movements, and it does update horizontally at the same time. It just doesn't
> move if you do a horizontal movement by itself. If the cursor movement commands aren't supported by
> PuTTY or by OpenSSH server+client, I would expect to see neither kind of movement working.
I don't know the answer, but I'm quite sure that if you look at the
sources of the respective packages, you will see the reason.
It is also possible that in cases where it worked Emacs decided to
move the cursor by redrawing the following or the preceding character,
instead of calling the console API functions. (These are redisplay
optimizations Emacs sometimes does.)
prev parent reply other threads:[~2021-01-26 15:07 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
2021-01-26 7:21 ` Ed Avis
2021-01-26 15:07 ` Eli Zaretskii [this message]
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=83h7n320uq.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).