zsh-workers
 help / color / mirror / code / Atom feed
From: Marlon Richert <marlon.richert@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Daniel Shahaf <d.s@daniel.shahaf.name>,
	Mikael Magnusson <mikachu@gmail.com>,
	 Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [PATCH] Remove redundancies from `git` completion
Date: Thu, 2 Sep 2021 09:17:25 +0300	[thread overview]
Message-ID: <CAHLkEDvnETmxUWen-o=oZtxDpfsZc3zNH2940j_6=7r4w=L+Fw@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7aB4QALHV0X5Q0fHeQQw=q+a9yP5-Kv7rRn5iOd131xhg@mail.gmail.com>

On Wed, Sep 1, 2021 at 9:23 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> On Wed, Sep 1, 2021 at 7:04 AM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> >
> > Anyone who wants to override them will still be able to do «autoload +X
> > _git && _git && _git-foo() { … }» (or a better solution which someone
> > will probably post in reply to this one).
>
> It would be nice if e.g. «autoload $HOME/gitfuncs/_git_foo» were
> sufficient, but the explicit definition of _git_foo inside _git will
> clobber that autoload.

Moving all _git_foo functions from the _git file into separate,
#autoload files would solve that.


  reply	other threads:[~2021-09-02 20:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-30 11:17 Marlon Richert
2021-08-30 11:41 ` Mikael Magnusson
2021-08-30 12:34   ` Marlon Richert
2021-08-30 12:42     ` Mikael Magnusson
2021-08-31  5:52       ` Marlon Richert
2021-09-01 14:03         ` Daniel Shahaf
2021-09-01 18:22           ` Bart Schaefer
2021-09-02  6:17             ` Marlon Richert [this message]
2021-09-02 20:51               ` Oliver Kiddle
2021-09-02 20:54                 ` Bart Schaefer
2021-09-02 21:17                   ` Oliver Kiddle
2021-09-01 13:56 ` Daniel Shahaf
2021-09-02  8:57   ` Marlon Richert

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='CAHLkEDvnETmxUWen-o=oZtxDpfsZc3zNH2940j_6=7r4w=L+Fw@mail.gmail.com' \
    --to=marlon.richert@gmail.com \
    --cc=d.s@daniel.shahaf.name \
    --cc=mikachu@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).