zsh-workers
 help / color / mirror / code / Atom feed
From: Greg Klanderman <gak@klanderman.net>
To: zsh-workers@zsh.org
Subject: Re: Tests of interrupting completion, and completion_nostat_dirs
Date: Wed, 05 Feb 2014 08:56:31 -0500	[thread overview]
Message-ID: <874n4dpss0.fsf@lwm.klanderman.net> (raw)
In-Reply-To: <140204212859.ZM21837@torch.brasslantern.com> (Bart Schaefer's message of "Tue, 04 Feb 2014 21:28:59 -0800")

>>>>> On February 5, 2014 Bart Schaefer <schaefer@brasslantern.com> wrote:

> Greg, I'm going to let Peter make the call on this one because he has
> become more concerned about namespace clutter that I.

> I would say that the change to ztat() should continue to read from a
> variable.  I think I'd have ztat() call getaparam() rather than declare
> a C array tied to a special variable (compare the way zle_refresh.c
> handles zle_highlight) but I'll stop at that.

Thank you Bart, the only downside I see is that I currently use the
existence of the special variable to decide whether to configure the
automount points in the fake-files zstyle, since I end up having to
kill my shell from another window if the automounts get configured in
a shell that doesn't have my patch and I ever hit tab to complete
under an automount.

If I use getaparam, is the only way to test if the feature exists with
a ZSH_VERSION / ZSH_PATCHLEVEL check?  Do we have any mechanism for
creating named features to test against?  Would it make sense to add a
readonly 'features' associative array (maybe in the zsh/parameter module)
whose keys are feature strings?

I'll wait to hear from Peter before doing anything..

Greg


  reply	other threads:[~2014-02-05 13:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACcU-g0qb3gZVLPPS2bQBixuozSsXd_9ObK+V6CTcaP4qfiFtA@mail.gmail.com>
     [not found] ` <140122000435.ZM1516@torch.brasslantern.com>
     [not found]   ` <CADdV=MsdfHUKDVy1dLbZ-d19cAEpGuDxzsKPd3Cy6imJ1Lo_8Q@mail.gmail.com>
     [not found]     ` <140123171659.ZM19422@torch.brasslantern.com>
     [not found]       ` <87iot91lp8.fsf@lwm.klanderman.net>
     [not found]         ` <140125124934.ZM23767@torch.brasslantern.com>
     [not found]           ` <87eh3q3g63.fsf@lwm.klanderman.net>
2014-01-30  2:12             ` Bart Schaefer
2014-01-30  9:30               ` Peter Stephenson
2014-01-30 16:22                 ` Bart Schaefer
2014-02-03 15:04                   ` Greg Klanderman
2014-02-05  5:28                     ` Bart Schaefer
2014-02-05 13:56                       ` Greg Klanderman [this message]
2014-02-05 14:23                         ` Peter Stephenson
2014-02-05 17:15                           ` Bart Schaefer
2014-02-05 17:36                             ` Peter Stephenson
2014-02-11 15:11                               ` Greg Klanderman

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=874n4dpss0.fsf@lwm.klanderman.net \
    --to=gak@klanderman.net \
    --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).