zsh-workers
 help / color / mirror / code / Atom feed
From: Stephane Chazelas <stephane@chazelas.org>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Roman Perepelitsa <roman.perepelitsa@gmail.com>,
	Millian Poquet <millian.poquet@irit.fr>,
	zsh-workers@zsh.org
Subject: Get cursor position (Was: [bug report] prompt can erase messages written on the terminal by background processes)
Date: Thu, 8 Dec 2022 08:21:03 +0000	[thread overview]
Message-ID: <20221208082103.zg44mrv77jrizsaj@chazelas.org> (raw)
In-Reply-To: <CAH+w=7aDn7SCv4Bao7ZQqtUaEv8EkvBXa15kM_nkF_GHLAcSFg@mail.gmail.com>

2022-12-07 19:46:37 -0800, Bart Schaefer:
[...]
> get_cursor_pos() {
>   print -n $'\e[6n'

Note that "print" already does \expansions without -r.

>   IFS=$'\e[;' read -s -d R -A ${1:-reply}

The query sequence could be sent using the prompt string (on
stderr):

IFS=$'\e[;' read -sd R -A ${1-reply}$'?\e[6n'

Then assuming "read -s" does the right thing and disables
line discipline echo before printing the prompt, that would
remove the risk of the terminal's reply coming before the echo
is disabled.

curpos() {
  IFS=$'\e[;' read -rsdR -t0.2 1$'?\e[6n' 1 ${2-y} ${1-x} 1 <> /dev/tty 2>&0
}
curpos col row


>   shift 3 ${1:-reply}

Shouldn't that be shift 2?

terminal should reply \e[y;xR, which would be split into ('' '' y x).

Or do a strict parsing of the reply:

curpos() {
  set -o localoptions -o extendedglob
  local match answer
  IFS= read -rsdR -t0.2 answer$'?\e[6n' &&
    [[ $answer = (#b)$'\e['(<->)';'(<->) ]] &&
    eval "${1-x}=\$match[2] ${2-y}=\$match[1]"

-- 
Stephane


  reply	other threads:[~2022-12-08  8:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07 19:02 [bug report] prompt can erase messages written on the terminal by background processes Millian Poquet
2022-12-07 22:55 ` Roman Perepelitsa
2022-12-08  3:46   ` Bart Schaefer
2022-12-08  8:21     ` Stephane Chazelas [this message]
2022-12-08  8:34       ` Get cursor position (Was: [bug report] prompt can erase messages written on the terminal by background processes) Roman Perepelitsa
2022-12-08 10:02         ` Stephane Chazelas
2022-12-08 10:10           ` Stephane Chazelas
2022-12-08 10:19           ` Mikael Magnusson
2022-12-09  2:19           ` Bart Schaefer
2022-12-09 12:46             ` Philippe Altherr
2022-12-10  4:30               ` Bart Schaefer
2022-12-10 14:55                 ` Private variables not private enough? (Was: Get cursor position (Was: [bug report] prompt can erase messages written on the terminal by background processes)) Philippe Altherr
2022-12-10 17:36                   ` Bart Schaefer
2022-12-10 20:38                     ` Bart Schaefer
2022-12-11 18:00               ` Get cursor position (Was: [bug report] prompt can erase messages written on the terminal by background processes) Stephane Chazelas
2022-12-09  1:39       ` Bart Schaefer
2022-12-08  8:45     ` [bug report] prompt can erase messages written on the terminal by background processes Roman Perepelitsa
2022-12-08 15:03     ` Oliver Kiddle

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=20221208082103.zg44mrv77jrizsaj@chazelas.org \
    --to=stephane@chazelas.org \
    --cc=millian.poquet@irit.fr \
    --cc=roman.perepelitsa@gmail.com \
    --cc=schaefer@brasslantern.com \
    --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).