From: Mikael Magnusson <mikachu@gmail.com>
To: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Cc: Daniel Shahaf <d.s@daniel.shahaf.name>, Zsh Users <zsh-users@zsh.org>
Subject: Re: Forgetting about compinit with manual alteration of _comps
Date: Wed, 10 Feb 2016 11:32:00 +0100 [thread overview]
Message-ID: <CAHYJk3ScBSP5ZoeZ-bJwfjQAGQgMvr34yC52d+rhnPyWH1D00w@mail.gmail.com> (raw)
In-Reply-To: <CAKc7PVDL3XfFmc7h23hjbybJ15k_hc_SZXkM-3WqzFCgOZshVw@mail.gmail.com>
On Wed, Feb 10, 2016 at 11:28 AM, Sebastian Gniazdowski
<sgniazdowski@gmail.com> wrote:
> On 10 February 2016 at 10:23, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>> However, I'm not sure making a plugin loadable _either before or after_
>> compinit is a good idea. It may be simpler for plugin authors to expect
>> to be loaded in one circumstance (say, after compinit) and ensure they
>> emit a clear error message in the other circumstance (say, before
>> compinit), than to eternally support two codepaths.
>
> All this is a frustration about "compinit does everything". If there
> was "compinit" and "compinit_examine_fpath", it would be all much
> simpler. User would init completion at beginning of .zshrc, which is a
> natural location for "init" things, and then "compinit_examine_fpath"
> at end, which is also natural. All this resolved by providing
> compdef() stub gathering compdef calls and allowing to replay them
> after compinit placed at bottom of .zshrc.
Another thought is designing a plugin interface designed around how
zsh actually works, rather than bending over backwards to accomodate
cargo culted code that barely works in the first place.
--
Mikael Magnusson
next prev parent reply other threads:[~2016-02-10 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKc7PVBLufmR3wLZ8mVGpGq1o1DgB8ci3bH3X6cyzbMyEOoZZg__29303.1625486494$1455013779$gmane$org@mail.gmail.com>
2016-02-10 9:23 ` Daniel Shahaf
2016-02-10 10:28 ` Sebastian Gniazdowski
2016-02-10 10:32 ` Mikael Magnusson [this message]
2016-02-10 11:02 ` Sebastian Gniazdowski
2016-02-09 10:28 Sebastian Gniazdowski
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=CAHYJk3ScBSP5ZoeZ-bJwfjQAGQgMvr34yC52d+rhnPyWH1D00w@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=d.s@daniel.shahaf.name \
--cc=sgniazdowski@gmail.com \
--cc=zsh-users@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).