zsh-workers
 help / color / mirror / code / Atom feed
From: Aleksandr Mezin <mezin.alexander@gmail.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: zsh-workers@zsh.org
Subject: Re: [RFC PATCH v3] vcs_info: choose backend by basedir
Date: Thu, 5 Nov 2020 06:50:25 +0600	[thread overview]
Message-ID: <CADnvcfJ4a6LdTTh2G1Vs4M7rgM3nm-9Qfhww=VYK5Me6tLBYsg@mail.gmail.com> (raw)
In-Reply-To: <20201104063824.74110106@tarpaulin.shahaf.local2>

On Wed, Nov 4, 2020 at 12:38 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> About extensibility, needs for extensibility aren't always foreseen.

I guess they can't be foreseen both ways, i.e. extensibility may be
needed where you didn't expect, but also maybe extensibility won't be
needed where you expected and designed. But creating a "more
extensible" interface takes more time, and this way you usually have
more complex code. So maybe this "premature extensibility" isn't worth
it?

>
> As to their own boolean styles, I'm not sure I agree.  zstyle values are
> arrays, so we could let parameters be provided in additional words, as
> in:
> .
>     zstyle $pattern $style enablement-order foo=bar
>     zstyle $pattern $style closest-.vcs-dir lorem=ipsum
>
> Hmm.  Perhaps it would make more sense to name the style "disk-layout",
> and then the extra parameters could be used to choose whether to select
> the closest or farthest .${vcs} dir.
>
> Or perhaps an enum really is overkill, as you say.

After your reply, for me it now seems to be even more overkill than before


  reply	other threads:[~2020-11-05  0:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29  1:27 Aleksandr Mezin
2020-10-29  2:26 ` Frank Terbeck
2020-10-30  6:55   ` Aleksandr Mezin
2020-10-30 16:47     ` Daniel Shahaf
2020-11-01 23:09 ` Aleksandr Mezin
2020-11-04  6:38   ` Daniel Shahaf
2020-11-05  0:50     ` Aleksandr Mezin [this message]
2020-11-05 14:49       ` Daniel Shahaf
2020-11-09 16:11         ` Aleksandr Mezin

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='CADnvcfJ4a6LdTTh2G1Vs4M7rgM3nm-9Qfhww=VYK5Me6tLBYsg@mail.gmail.com' \
    --to=mezin.alexander@gmail.com \
    --cc=d.s@daniel.shahaf.name \
    --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).