From: Daniel Tameling <tamelingdaniel@gmail.com>
To: zsh-workers@zsh.org
Subject: Re: support more arguments to diff
Date: Mon, 16 Apr 2018 16:59:13 +0200 [thread overview]
Message-ID: <20180416145913.wv637mfnw5hfe2fi@Daniels-MacBook-Air.local> (raw)
In-Reply-To: <CAF6rxgmh+N8VdjzN-jGA4QHPJANLkMJ-JZXChb-28DZxxLVa7Q@mail.gmail.com>
On Sun, Apr 15, 2018 at 10:48:08PM -0700, Eitan Adler wrote:
> This patch isn't perfect since {Net,DragonFly,Open,Free}BSD are not
> identical but this patch at leasts makes the completion a lot closer
> to reality.
>
> Currently FreeBSD doesn't even show -q for example.
>
Did the patch change the behavior of diff completion for you? On my
FreeBSD, diff is some GNU variant, and I think that it's the default
and that I didn't install it via pkg:
$ uname -sr
FreeBSD 11.1-RELEASE-p9
$ which diff
/usr/bin/diff
$ diff -v
diff (GNU diffutils) 2.8.7
Written by Paul Eggert, Mike Haertel, David Hayes,
Richard Stallman, and Len Tower.
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
If completing, I also get the GNU options. -q appears actually on the
first line:
$ diff -<Tab>
Completing option
--brief -q -- output only whether files = differ
.....
I think the reason why there is only openbsd in the else branch is
that all the other ship with some kind of GNU diff. (At least that is
what the online man pages of dragonfly and netbsd indicate.) However,
the versions seem to differ wildly across BSDs.
--
Kind regards,
Daniel
next prev parent reply other threads:[~2018-04-16 14:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 5:48 Eitan Adler
2018-04-16 14:59 ` Daniel Tameling [this message]
2018-04-17 11:22 ` Eitan Adler
2018-04-17 12:53 ` Matthew Martin
2018-04-18 0:37 ` Eitan Adler
2018-04-18 9:22 ` Oliver Kiddle
2018-04-18 9:36 ` Eitan Adler
2018-08-29 14:56 ` Oliver Kiddle
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=20180416145913.wv637mfnw5hfe2fi@Daniels-MacBook-Air.local \
--to=tamelingdaniel@gmail.com \
--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).