From: Bart Schaefer <schaefer@brasslantern.com>
To: Philippe Altherr <philippe.altherr@gmail.com>
Cc: zsh-workers@zsh.org
Subject: Re: Get cursor position (Was: [bug report] prompt can erase messages written on the terminal by background processes)
Date: Fri, 9 Dec 2022 20:30:03 -0800 [thread overview]
Message-ID: <CAH+w=7Z9x7fqLA=01GDYBRTnoDqs7MySZtQwZevE_O6Lyzew7g@mail.gmail.com> (raw)
In-Reply-To: <CAGdYchvNLkmDcPWRXrrmH6r7qZUt8PojXpVcZSagiRMDUVx9Wg@mail.gmail.com>
On Fri, Dec 9, 2022 at 4:46 AM Philippe Altherr
<philippe.altherr@gmail.com> wrote:
>
> I just stumbled on the module zsh/param/private, which makes it possible (but I won't claim that it's very practical):
>[...]
> It's a bit strange that the initialization is needed. Private variables don't hide global variables of the same name, nor prevent their assignment, but prevent their initial declaration.
This isn't exactly an effect of private, it's the previously observed
effect that there is no way to "unlocal" a parameter in the current
scope, so you have to add it to the desired scope before declaring it
local.
> assign() {
> print -v "$1" "$2"
> }
You don't actually need a named function or print -v here, although I
guess "print -v" is shorter to write than "typeset -g".
curpos() {
set -o localoptions -o extendedglob
eval "${1-x}= ${2-y}="
zmodload zsh/param/private
local -P -a match mbegin mend
local -P answer
IFS= read -rsdR -t0.2 answer$'?\e[6n' &&
[[ $answer = (#b)$'\e['(<->)';'(<->) ]] &&
() { typeset -g "$1"="$2" } ${1-x} "$match[2]" &&
() { typeset -g "$1"="$2" } ${2-y} "$match[1]"
}
I'm torn about that eval-as-delcarator. My first thought would be to use
typeset -gi ${1-x} ${2-y}
but the eval avoids changing any declared flags on existing parameters
in the enclosing scope. On the other hand both that eval and the use
of "print -v" force the variables to be scalar, whereas "typeset -g"
throws errors on assignment mismatch.
next prev parent reply other threads:[~2022-12-10 4:30 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
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 [this message]
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='CAH+w=7Z9x7fqLA=01GDYBRTnoDqs7MySZtQwZevE_O6Lyzew7g@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=philippe.altherr@gmail.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).