From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: UNDO_LIMIT_NO and its documentation
Date: Tue, 18 Aug 2015 09:26:43 +0100 [thread overview]
Message-ID: <20150818092643.1aa9ce9b@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <150818000916.ZM28704@torch.brasslantern.com>
On Tue, 18 Aug 2015 00:09:16 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> The doc says:
>
> A typical use of this variable in a widget function is as follows:
>
> integer save_limit=$UNDO_LIMIT_NO
> UNDO_LIMIT_NO=$UNDO_CHANGE_NO
> {
> # Perform some form of recursive edit.
> } always {
> UNDO_LIMIT_NO=save_limit
> }
>
> Firstly, why not just
>
> local UNDO_LIMIT_NO=$UNDO_CHANGE_NO
>
> and allow function scoping to restore it?
As noted in the comments when the patch appeared, you'd need double
function scope because of the way ZLE widgets work. I couldn't be
bothered to explain, but surrounding the code with (){ ... } should be
OK in principle.
> It's not a special.
All ZLE parameters are special, but removable. See makezleparams().
> Secondly, declaring "integer save_limit" means that save_limit will have
> a default of zero, but UNDO_LIMIT_NO has a default of unset. So when the
> assignment back to UNDO_LIMIT_NO is done, it'll change state from unset
> to zero. Does that matter?
It should work fine, but I can't find any evidence in zle_params.c that
UNDO_LIMIT_NO is unset; only NUMERIC has that behaviour at the moment.
Either it's present as an integer variable or it isn't.
pws
next prev parent reply other threads:[~2015-08-18 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 7:09 Bart Schaefer
2015-08-18 8:26 ` Peter Stephenson [this message]
2015-08-18 9:17 ` Peter Stephenson
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=20150818092643.1aa9ce9b@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.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).