From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Complete global aliases?
Date: Sun, 18 Sep 2022 11:43:15 +0200 [thread overview]
Message-ID: <CAKc7PVDXLRd0u2cinG-Q5VrTng9aqkZieAEg64szH2JZxT36VQ@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7bocHLgfzi4x7G3o_+a+N8WTVaoxkjiF67e6=9tPJjeoQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]
On Sun, 18 Sept 2022 at 01:27, Bart Schaefer <schaefer@brasslantern.com>
wrote:
> On Sat, Sep 17, 2022 at 7:27 AM Sebastian Gniazdowski
> <sgniazdowski@gmail.com> wrote:
> >
> > I think that the global aliases should be completed out of the box, what
> do you say?
>
> I think there needs to be a bit more specification about how this would
> work.
>
> Where would this fit in the overall design of contexts? E.g. does it
> happen in "-default-" context (which isn't always applied) and if so
> do alaises complete instead of files, as well as files, or only when
> there are no files (that is, _files returns nonzero)?
>
I'm not sure, however there's a solution on the web, see:
https://stackoverflow.com/a/59513051/11999858
>
> Do the aliases expand or is just their name completed?
I think that only its name should be completed.
> What happens
> if you complete to the right of a global alias that (if expanded)
> changes the syntax of the command line
I think that it shouldn't be expanded, so the issue isn't actual.
--
Best regards,
Sebastian Gniazdowski
[-- Attachment #2: Type: text/html, Size: 2724 bytes --]
next prev parent reply other threads:[~2022-09-18 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 14:20 Sebastian Gniazdowski
2022-09-17 23:27 ` Bart Schaefer
2022-09-18 9:43 ` Sebastian Gniazdowski [this message]
2022-09-19 1:46 ` Bart Schaefer
2022-09-24 11:02 ` Sebastian Gniazdowski
2022-09-18 2:11 ` Eric Cook
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=CAKc7PVDXLRd0u2cinG-Q5VrTng9aqkZieAEg64szH2JZxT36VQ@mail.gmail.com \
--to=sgniazdowski@gmail.com \
--cc=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).