zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: dana <dana@dana.is>, Amyn Bennamane <amynbe@gmail.com>,
	 "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Git-add completion should show full file paths
Date: Tue, 28 Apr 2020 20:42:16 -0700	[thread overview]
Message-ID: <CAH+w=7bO57UHB2-iJzG=TSnbHL8CQ-yZyg5Pv=+obXjPJNF3ag@mail.gmail.com> (raw)
In-Reply-To: <20200428180118.26e97826@tarpaulin.shahaf.local2>

On Tue, Apr 28, 2020 at 11:01 AM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> Bart Schaefer wrote on Mon, 27 Apr 2020 21:35 -0700:
> > ... call something OTHER THAN _multi_parts if you don't want the
> > strings treated as having multiple parts?
>
> That'd force everyone to use the "list of all files" semantics.

I don't mean unconditionally call something else.  I mean, check a
style and either call _multi_parts, or not.

> > That could be put into a wrapper function around the two possible
> > _wanted calls above, if it were desirable to have it somewhere other
> > than in _git_files.
>
> Seems like this would also allow people to use «zstyle -e» to choose
> between the two behaviours dynamically, which could be used to
> implement the "if there are more than x files" semantics dana described.

Yes, or the algorithm for that could be built into the wrapper and
activated by a style value.

  reply	other threads:[~2020-04-29  3:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-26 22:57 Amyn Bennamane
2020-04-27 19:25 ` dana
2020-04-28  4:35   ` Bart Schaefer
2020-04-28 18:01     ` Daniel Shahaf
2020-04-29  3:42       ` Bart Schaefer [this message]
2020-04-29  9:21         ` Daniel Shahaf

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='CAH+w=7bO57UHB2-iJzG=TSnbHL8CQ-yZyg5Pv=+obXjPJNF3ag@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=amynbe@gmail.com \
    --cc=d.s@daniel.shahaf.name \
    --cc=dana@dana.is \
    --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).