zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: PATCH: completion for a few more coreutils things
Date: Wed, 11 Oct 2017 17:56:10 +0000	[thread overview]
Message-ID: <1507744570.3516372.1135550888.78DF91BE@webmail.messagingengine.com> (raw)
In-Reply-To: <171011094518.ZM20771@torch.brasslantern.com>

Bart Schaefer wrote on Wed, 11 Oct 2017 09:45 -0700:
> On Oct 11,  1:23am, Daniel Shahaf wrote:
> } Subject: Re: PATCH: completion for a few more coreutils things
> }
> } Oliver Kiddle wrote on Tue, 10 Oct 2017 11:16 +0200:
> } > Jun T wrote:
> } > > The file Completion/Unix/Command/_expand need be renamed because _expand
> } > > already exists in Completion/Base/Completer/_expand.
> } > 
> } > Oh yes. That'll break things fairly badly, sorry.
> } 
> } Can we make this situation a build error in the future?
> 
> Having two files with the same name is not necessarily an error; the
> intent has been that we might have one file for openSUSE and another
> for Solaris, etc., and the local packager was responsible for putting
> the correct one in the installation (or correct directory in fpath).
> 
> (On the other hand we've never given much configure/install help for
> how to select the right one.)
> 
> Two files with the same name and incompatible #compdef lines is another
> matter, but I don't have any good ideas for determining "incompatible."

"Not in a whitelist of known-good collisions"

I.e., default to erroring out on all collisions except those specifically whitelisted.

Just an idea...

Daniel


      reply	other threads:[~2017-10-11 17:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-06 22:16 Oliver Kiddle
2017-10-10  6:18 ` Jun T
2017-10-10  8:57   ` Peter Stephenson
2017-10-10  9:16   ` Oliver Kiddle
2017-10-11  1:23     ` Daniel Shahaf
2017-10-11 16:45       ` Bart Schaefer
2017-10-11 17:56         ` Daniel Shahaf [this message]

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=1507744570.3516372.1135550888.78DF91BE@webmail.messagingengine.com \
    --to=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).