From: Pier Paolo Grassi <pierpaolog@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh-Users List <zsh-users@zsh.org>
Subject: Re: completion functions not loaded
Date: Sun, 12 Feb 2023 18:22:47 +0100 [thread overview]
Message-ID: <CAP+y1xDiNWDKsZJXNoxMFG-c+yKsestDfD1Ba4dSP1QrRXziGw@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7b0N-Da3eK1Q7=Wv-cDnHN+c-djt_bddyhUhys2cdF2+g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
echo $_comps[systemctl]
_systemctl
I think that is the only definition of this function that I have
the strange thing is that it's not autoloaded even if it is scheduled to do
so
is it possibile that some error prevents it from loading?
Pier Paolo Grassi
Il giorno sab 11 feb 2023 alle ore 22:31 Bart Schaefer <
schaefer@brasslantern.com> ha scritto:
> On Sat, Feb 11, 2023 at 1:27 PM Bart Schaefer <schaefer@brasslantern.com>
> wrote:
> >
> > > What can I do to debug the issue?
> >
> > Check that the file starts with either
> >
> > #compdef ...
> >
> > or
> >
> > #autoload
>
> Sorry, accidentally sent too soon.
>
> And that the #compdef line mentions the "systemctl" command. You can
> also check $_comps[systemctl], it's possible that something else
> loaded later is replacing it.
>
--
Pier Paolo Grassi
[-- Attachment #2: Type: text/html, Size: 1696 bytes --]
next prev parent reply other threads:[~2023-02-12 17:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 21:18 Pier Paolo Grassi
2023-02-11 21:27 ` Bart Schaefer
2023-02-11 21:30 ` Pier Paolo Grassi
2023-02-11 21:31 ` Bart Schaefer
2023-02-12 17:22 ` Pier Paolo Grassi [this message]
2023-02-12 17:41 ` Bart Schaefer
2023-02-12 17:52 ` Pier Paolo Grassi
2023-02-12 18:13 ` Pier Paolo Grassi
2023-02-12 18:27 ` Pier Paolo Grassi
2023-02-12 18:36 ` Roman Perepelitsa
2023-02-12 20:58 ` Pier Paolo Grassi
2023-02-12 21:08 ` Roman Perepelitsa
2023-02-12 21:09 ` Pier Paolo Grassi
2023-02-12 21:53 ` Bart Schaefer
2023-02-13 8:23 ` Roman Perepelitsa
2023-02-13 10:01 ` Pier Paolo Grassi
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=CAP+y1xDiNWDKsZJXNoxMFG-c+yKsestDfD1Ba4dSP1QrRXziGw@mail.gmail.com \
--to=pierpaolog@gmail.com \
--cc=schaefer@brasslantern.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).