zsh-workers
 help / color / mirror / code / Atom feed
From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: "Yannic Schröder" <schroeder@ibr.cs.tu-bs.de>
Cc: zsh-workers@zsh.org
Subject: Re: Incorrect cursor position when ZLE_RPROMPT_INDENT=0 (with a fix)
Date: Mon, 20 May 2019 10:36:05 +0200	[thread overview]
Message-ID: <CAN=4vMo9oZ19n5kwNiNDjSHQAnNJHXRBPSfZstN7QOvXgN3WrQ@mail.gmail.com> (raw)
In-Reply-To: <68081d8c-1aa6-203b-eb6c-e2d048de1340@ibr.cs.tu-bs.de>

[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]

On Mon, May 20, 2019 at 10:22 AM Yannic Schröder <schroeder@ibr.cs.tu-bs.de>
wrote:

> Maybe add some of the common alternative Linux terminals to the test?
> Like Terminator and Tilix?
>

Thanks for the advice. Just tested these. I also added XTerm to the list.
They all behave as the other terminals I've tested yesterday.

So far I've tested 9 terminals on 3 operating systems. They all behave
identically without my patch (the cursor position is off by one) and with
my patch (the cursor position is correct).

I suppose there should be a terminal on which the unpatched ZSH works
correctly but so far I haven't found it. I'd really like to. If anyone here
is using a terminal for which the following test works, please give a
holler.

1. Type `zsh -df`.
2. Type `ZLE_RPROMPT_INDENT=0 PROMPT=12 RPROMPT=3`.
3. Observe the position of the cursor. The correct position is after '2'.
All terminals I've tested put cursor on '2' -- one position to the left of
correct.

Roman.

  reply	other threads:[~2019-05-20  8:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-19 15:38 Roman Perepelitsa
2019-05-19 15:41 ` Roman Perepelitsa
2019-05-19 17:04 ` Bart Schaefer
2019-05-19 17:34   ` Roman Perepelitsa
2019-05-19 18:09     ` Roman Perepelitsa
2019-05-19 18:51       ` Roman Perepelitsa
2019-05-19 20:12         ` Bart Schaefer
2019-05-19 21:07           ` Roman Perepelitsa
2019-05-20  8:21             ` Yannic Schröder
2019-05-20  8:36               ` Roman Perepelitsa [this message]
2019-05-20 10:21                 ` Charles Blake
2019-05-20 10:46                   ` Roman Perepelitsa
2019-05-20 11:06                     ` Daniel Shahaf
2019-05-20 11:07                     ` Charles Blake
2019-05-20 11:11                       ` Peter Stephenson
2019-05-20 11:32                       ` Roman Perepelitsa
2019-05-20 12:41                     ` Charles Blake
2019-05-20 13:16                       ` Roman Perepelitsa
     [not found]                         ` <CAKiz1a-nOkAe42JoxFRgMJ+LXZ3fgMxqgwNZOW+2Y45oqzu8hA@mail.gmail.com>
2019-05-20 13:55                           ` Roman Perepelitsa
2019-05-23  5:48                             ` Roman Perepelitsa
2019-05-23 21:36                               ` Daniel Shahaf
2019-05-23 22:52                                 ` Roman Perepelitsa
2019-05-24 12:18                                   ` Daniel Shahaf
2019-05-27 15:36                                     ` Roman Perepelitsa
2019-05-27 21:51                                       ` Peter Stephenson
2019-05-28  8:44                                         ` Peter Stephenson
2019-05-28  8:46                                           ` Roman Perepelitsa
2019-05-28 14:26                                         ` Bart Schaefer

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='CAN=4vMo9oZ19n5kwNiNDjSHQAnNJHXRBPSfZstN7QOvXgN3WrQ@mail.gmail.com' \
    --to=roman.perepelitsa@gmail.com \
    --cc=schroeder@ibr.cs.tu-bs.de \
    --cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).