From: Stephane Chazelas <stephane@chazelas.org>
To: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Cc: Bart Schaefer <schaefer@brasslantern.com>,
Millian Poquet <millian.poquet@irit.fr>,
zsh-workers@zsh.org
Subject: Re: Get cursor position (Was: [bug report] prompt can erase messages written on the terminal by background processes)
Date: Thu, 8 Dec 2022 10:02:15 +0000 [thread overview]
Message-ID: <20221208100215.k2qcqdqgjlzwbdh7@chazelas.org> (raw)
In-Reply-To: <CAN=4vMrSO99rKMGhmO_yjtqYLUf+senu=Lhb=F47a9S6y8d7Hw@mail.gmail.com>
2022-12-08 09:34:41 +0100, Roman Perepelitsa:
[...]
> > 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]"
> > }
>
> Functions that accept output parameter names as arguments are tricky.
> The following won't work:
>
> # Which line is the cursor on?
> curpos _ answer
> print -r -- "The cursor is on the line number $answer"
[...]
Yes, I thought of using 3 as the intermediary variable, but
decided against it as we can't do anything about match,
mbegin... anyway.
typeset -g "${1-x}=$match[2]" "${2-y}=$match[1]"
Doesn't work either. I guess there's no way to access variables
by the same name in that parent scope or to unlocal a variable?
(bash does by exploiting some bug (calling unset -v in a
severate function peels one layer of scoping instead of
unsetting in the current scope)).
--
Stephane
next prev parent reply other threads:[~2022-12-08 10:02 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 ` Get cursor position (Was: [bug report] prompt can erase messages written on the terminal by background processes) Stephane Chazelas
2022-12-08 8:34 ` Roman Perepelitsa
2022-12-08 10:02 ` Stephane Chazelas [this message]
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=20221208100215.k2qcqdqgjlzwbdh7@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).