From: Bart Schaefer <schaefer@brasslantern.com>
To: "zsh workers" <zsh-workers@sunsite.dk>
Subject: Re: Change in FIGNORE behavior
Date: Wed, 30 May 2007 03:58:10 -0700 [thread overview]
Message-ID: <070530035810.ZM29792@torch.brasslantern.com> (raw)
In-Reply-To: <20070530112934.3950357b@news01.csr.com>
On May 30, 11:29am, Peter Stephenson wrote:
}
} I've found what's causing it by using the default set of completers: it's
} the effect of the change in (R) on this code in _ignored:
}
} zstyle -a ":completion:${curcontext}:" completer comp ||
} comp=( "${(@)_completers[1,_completer_num-1][(R)_ignored(|:*),-1]}" )
I knew something was nagging me about that change to (R). Here's
another thing that I just remembered:
var[(R)pattern] is an assignable construct. Previously
var[(R)missing]=something
would replace the first element. Now it appends an element to the end.
You might think this is inconsequential until you remember that
var[(R)missing]=( a whole lot of something )
will now append the entire new array, whereas before it spliced the
new elements into the front of the old array.
That's going to bite somebody ... in fact I appear to have a script
that relies on the old behavior, although it's one I haven't used in
a long time.
next prev parent reply other threads:[~2007-05-30 10:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 1:56 Vin Shelton
2007-05-30 9:45 ` Peter Stephenson
2007-05-30 10:29 ` Peter Stephenson
2007-05-30 10:58 ` Bart Schaefer [this message]
2007-05-30 11:27 ` Peter Stephenson
2007-05-30 12:54 ` Peter Stephenson
2007-06-04 9:49 ` Peter Stephenson
2007-06-04 16:56 ` Bart Schaefer
2007-06-05 14:19 ` Peter Stephenson
2007-06-15 10:09 ` Peter Stephenson
2007-06-15 10:22 ` Stephane Chazelas
2007-06-15 10:30 ` Peter Stephenson
2007-06-18 13:32 ` Peter Stephenson
2007-06-20 5:13 ` Version emulation (Re: Change in FIGNORE behavior) Bart Schaefer
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=070530035810.ZM29792@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/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).