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 19:27:09 +0100 [thread overview]
Message-ID: <CAP+y1xB6LM8yW02cEZZab11dTvZKZ35fOmX+U6kR33zKWzdA+w@mail.gmail.com> (raw)
In-Reply-To: <CAP+y1xA8d3nhnCwj-Jo9Z=v=igLfxfyY7p1b5+rVF7UhJTwukw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1431 bytes --]
sorry, too soon...
autoload +X _systemctl
does not produce any output, but it does not gives an error though
but the completion context for systemctl does not change, _systemctl is not
present,
even after a
compdef _systemctl systemctl
but functions _systemctl now returns the correctly loaded function body
Pier Paolo Grassi
Il giorno dom 12 feb 2023 alle ore 19:13 Pier Paolo Grassi <
pierpaolog@gmail.com> ha scritto:
> autoload +X _systemctl
>
> does not produce any output, but it does not gives an error though
> but the completion context for systemctl does not change, _systemctl is
> not present
>
> Pier Paolo Grassi
>
>
> Il giorno dom 12 feb 2023 alle ore 18:52 Pier Paolo Grassi <
> pierpaolog@gmail.com> ha scritto:
>
>> It doesn't seem to do anything. Even inserting
>> setopt xtrace
>>
>> just after #compdef systemctl
>> in /usr/share/zsh/vendor-completions/_systemctl does not produce any output
>> when trying to complete the systemctl command after opening a new shell
>>
>> Pier Paolo Grassi
>>
>>
>> Il giorno dom 12 feb 2023 alle ore 18:41 Bart Schaefer <
>> schaefer@brasslantern.com> ha scritto:
>>
>>> On Sun, Feb 12, 2023 at 9:23 AM Pier Paolo Grassi <pierpaolog@gmail.com>
>>> wrote:
>>> >
>>> > 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?
>>>
>>> Yes; try
>>> autoload +X _systemctl
>>>
>>
[-- Attachment #2: Type: text/html, Size: 2995 bytes --]
next prev parent reply other threads:[~2023-02-12 18:28 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
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 [this message]
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+y1xB6LM8yW02cEZZab11dTvZKZ35fOmX+U6kR33zKWzdA+w@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).