git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Лёша Огоньков" <lesha.ogonkov@gmail.com>
Cc: Stefan Haller <lists@haller-berlin.de>,
	Felipe Contreras <felipe.contreras@gmail.com>,
	Alexey via GitGitGadget <gitgitgadget@gmail.com>,
	Git <git@vger.kernel.org>
Subject: Re: [PATCH] Fix zsh installation instructions
Date: Tue, 27 Oct 2020 13:00:13 -0700	[thread overview]
Message-ID: <xmqqwnzbbfsi.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <CAKU+SVKad4q-2tTrYXa+DJBz5UJOtndEe3-4Uvnd5GZ92543ng@mail.gmail.com> (=?utf-8?B?ItCb0ZHRiNCwINCe0LPQvtC90YzQutC+0LIiJ3M=?= message of "Tue, 27 Oct 2020 11:59:20 +0300")

Лёша Огоньков  <lesha.ogonkov@gmail.com> writes:

> On Tue, 27 Oct 2020 at 11:32, Stefan Haller <lists@haller-berlin.de> wrote:
>>
>> On 25.10.20 4:29, Felipe Contreras wrote:
>> >> The other hunk (adding compinit) is not so important to me; I suppose it
>> >> was not in the original version because most zsh users already have this
>> >> in their .zshrc anyway. But it's not wrong, and doesn't hurt to have
>> >> here, I guess.
>> >
>> > If you don't have compinit, then how is the '_git' script being loaded
>> > in the first place?
>>
>> I didn't say it's unnecessary to have it in your .zshrc. I just said
>> it's maybe unnecessary to document it here because most zsh users have
>> it in their .zshrc already anyway.
>
> As an inexperienced zsh user it took me ages to understand why the
> whole thing is not working.

So,... even though it may look to more experienced zsh users that it
is unnecessary to document it in this file, in your opinion, it is a
good idea to mention "compinit" to help less experienced users?

In any case, the patch in question is the only thing in flight that
conflicts with Felipe's 29 patch series, and the change to zstyle
line is common between both efforts, so it is just between adding
the "autoload -Uz compinit && compinit" near the fpath=(...) thing
or leaving it out.

I'll let those who know zsh to figure it out.  I suspect that the
resolution would be either to ask Felipe to rebase his on yours,
rebase yours on top of Felipe's, or just drop yours (if "autoload"
thing is unnecessary as Stefan suspects---I cannot tell what Felipe
wants to suggest by his response, between "unless you have compinit
you wouldn't be using this script so why write it?" and "your users
need to be taught about the need _somehow_, so why not make this the
place to do so?").

Thanks.

  reply	other threads:[~2020-10-27 20:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 10:51 [PATCH] Fix zsh installation instructions Alexey via GitGitGadget
2020-07-06 22:42 ` Junio C Hamano
2020-10-14 15:10   ` Stefan Haller
2020-10-16 17:06     ` Junio C Hamano
2020-10-25  3:29     ` Felipe Contreras
2020-10-27  8:29       ` Stefan Haller
2020-10-27  8:32       ` Stefan Haller
2020-10-27  8:59         ` Лёша Огоньков
2020-10-27 20:00           ` Junio C Hamano [this message]
2020-10-28  1:45             ` Felipe Contreras
2020-10-29 17:50               ` Junio C Hamano
2020-10-29 19:09                 ` Junio C Hamano
2020-11-02 20:49                 ` Felipe Contreras
2020-11-02 20:54                   ` Felipe Contreras
2020-11-03  1:02                     ` Junio C Hamano
2020-11-02 22:37                   ` Junio C Hamano
2020-10-28  1:31           ` Felipe Contreras

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=xmqqwnzbbfsi.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=lesha.ogonkov@gmail.com \
    --cc=lists@haller-berlin.de \
    /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.
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).