From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Bart Schaefer" <schaefer@candle.brasslantern.com>,
"ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: RE: GNU diff completion problem
Date: Fri, 10 Mar 2000 10:02:58 +0300 [thread overview]
Message-ID: <000d01bf8a5e$aadd9330$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <1000309182247.ZM10799@candle.brasslantern.com>
>
> On Mar 9, 7:45pm, Andrej Borsenkow wrote:
> } Subject: GNU diff completion problem
> }
> } I'm sorry, but I missed this discussion.
> }
> } Why _diff_options tests diff and not real command ($word[1])?
>
> It's in case the real command is an alias or function that has unknown
> side-effects.
>
But this applies just as well to any other possible command that has GNU counterpart and
needs version check. What is so different with diff?
> } I have system default diff and GNU diff as gdiff. Current state does not
> } allow me to complete GNU diff at all
>
> You want
>
> compdef _diff gdiff
> zstyle ':completion:*:*:gdiff:*:version' command gdiff -v
>
Nope. I do want
compdef _diff diff gdiff
without bothering, if GNU diff is installed as main or additional program. The above will
cover 99.9% of installations.
I agree with the point, that _diff_options can be called in context without actual
command. But it simply means, that _diff_options should not test diff version itself, but
just get a "diff kind" parameter. Actual testing is to be done by _diff.
-andrej
next prev parent reply other threads:[~2000-03-10 7:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-09 16:45 Andrej Borsenkow
2000-03-09 17:30 ` Alexandre Duret-Lutz
2000-03-09 18:22 ` Bart Schaefer
2000-03-10 7:02 ` Andrej Borsenkow [this message]
2000-03-10 9:01 Sven Wischnowsky
2000-03-10 11:24 ` Bart Schaefer
2000-03-10 12:52 ` Alexandre Duret-Lutz
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='000d01bf8a5e$aadd9330$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.dk \
/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).