zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@ifh.de>
To: zsh-workers@math.gatech.edu (Zsh hackers list)
Subject: Re: ZLE special parameters
Date: Mon, 24 Mar 1997 10:54:41 +0100	[thread overview]
Message-ID: <199703240954.KAA23113@hydra.ifh.de> (raw)
In-Reply-To: "Zefram"'s message of "Sat, 22 Mar 1997 16:36:55 MET." <13344.199703221636@stone.dcs.warwick.ac.uk>

Zefram wrote:
> Incidentally, if I read the unset code correctly, a parameter created
> within a function using typeset can actually be removed by a nested
> function using unset, although it can't be removed by the function itself.
> Is this POSIX behaviour, desirable, neither or both?

This is probably wrong.  There was an exchange between Bart and me
about funny things with typeset and local variables some time ago.  It
needs rewriting.

I'm getting a core dump with the increment function: it's quite
possible I've missed some necessary intermediate patch, though; the
number pending is rather large at the moment.

% zle -N increment
% bindkey \^xi increment
% echo 38

Hitting ^xi twice gives a core dump.  Any modification of LBUFFER
seems to do this.  It's coming in makezleparams(); createparam() is
returning a NULL because the (oldpm && !(oldpm->flags & PM_UNSET))
test failed.  Oddly enough, it's always when zp->name is BUFFER even
if I only change LBUFFER.  Even if I am missing a patch, I worry about
relying on the parameter not already existing at this point.

-- 
Peter Stephenson <pws@ifh.de>       Tel: +49 33762 77366
WWW:  http://www.ifh.de/~pws/       Fax: +49 33762 77413
Deutsches Elektronen-Synchrotron --- Institut fuer Hochenergiephysik Zeuthen
DESY-IfH, 15735 Zeuthen, Germany.


  reply	other threads:[~1997-03-24 10:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-03-22 16:36 Zefram
1997-03-24  9:54 ` Peter Stephenson [this message]
1997-03-24 18:50   ` Zefram

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=199703240954.KAA23113@hydra.ifh.de \
    --to=pws@ifh.de \
    --cc=zsh-workers@math.gatech.edu \
    /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).