From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Tests of interrupting completion, and completion_nostat_dirs
Date: Thu, 30 Jan 2014 08:22:06 -0800 [thread overview]
Message-ID: <140130082206.ZM23682@torch.brasslantern.com> (raw)
In-Reply-To: <20140130093057.6e04fa53@pwslap01u.europe.root.pri>
On Jan 30, 9:30am, Peter Stephenson wrote:
} Subject: Re: Tests of interrupting completion, and completion_nostat_dirs
}
} On Wed, 29 Jan 2014 18:12:06 -0800
} Bart Schaefer <schaefer@brasslantern.com> wrote:
} > Hmm, to include this I'd probably want completion_nostat_dirs to be an
} > autoloaded parameter in the zsh/complete module or something like that.
} > It doesn't have any of those right now (the magic parameters that are
} > only valid inside completion widgets are a somewhat different beast) but
} > there's no reason it couldn't.
}
} This has traditionally been done using something that's only seen by
} completion that gets passed in from above.
Yes, but in this case there's a corresponding C code change to recognize
the setting.
} It could, for example, be something in compstate set at the top level
} of _main_complete, but there are other mechanisms: the menu completion
} library uses its own parameters that are set by styles, and sometimes
} the effect of styles get passed into builtins which probably doesn't
} fit here.
I suppose the parameter *could* in fact be valid only when inside a
completion widget, and it would then be up to _main_complete to copy
from a zstyle into the parameter so that ztat() could see it. That
would be roughly the same as the treatment of region_highlight by zle;
it doesn't exist except while doing its job.
Of course that would mean that compctl and/or widgets entered directly
without going through _main_complete would need to do their own zstyle
lookup. This is the reason that e.g. MENUSCROLL is a global parameter
as well as being copied from a zstyle.
} This is different from ZLE which doesn't use styles so gets configured
} by straight parameters --- that's not ideal; it would be better to use
} some form of namespace if we could.
Right, but the completion-only scoping could stand in for that in the
case of completion. The "problem" for zle is that, unless we actually
make the internals aware of zstyle values at the C level, there's no
guaranteed entry point where a zstyle can be referenced by shell code.
(zle-line-init could serve that role now, I suppose, but then everyone
needs a default zle-line-init [compare MENUSCROLL above].)
next prev parent reply other threads:[~2014-01-30 16:22 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 [this message]
2014-02-03 15:04 ` Greg Klanderman
2014-02-05 5:28 ` Bart Schaefer
2014-02-05 13:56 ` Greg Klanderman
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=140130082206.ZM23682@torch.brasslantern.com \
--to=schaefer@brasslantern.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).