Date: Sat, 15 Feb 2020 18:38:03 +1300 From: Fehmi Noyan ISI <fnoyanisi@yahoo.com> To: freebsd-hackers@freebsd.org Subject: diff(1) -c and -u options Message-ID: <83CB71EA-714E-4C91-9E2B-143A0E222D37@yahoo.com> References: <83CB71EA-714E-4C91-9E2B-143A0E222D37.ref@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
I am working on same changes to diff(1) (bug 243975) and noticed that one of=
the atf tests does this (in /usr/src/usr.bin/diff/tests/diff_test.sh unifie=
d_body())
atf_check -o file:$(atf_get_srcdir)/unified_c9999.out -s eq:1 \
diff -u -c9999 -L input_c1.in -L input_c2.in "$(atf_get_srcdir)/input=
_c1.in" "$(atf_get_srcdir)/input_c2.in=E2=80=9D
when I try it out myself, -u -cNUM and -cNUM give the same output, making -u=
redundant here.
GNU diff complains about incompatible output styling when -u -c are passed a=
s arguments at the same time.
I would assume -u -cNUM was used to limit the number of output lines but the=
same can be achieved by -uNUM anyway.
I thought about removing this test case since it does not test anyting relat=
ed to unified output (-u) (? here) but did not feel comfortable about it and=
though it would be worthwhile to send an email to freebsd-hackers first.
Any thoughts?
Ta
Fehmi=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?83CB71EA-714E-4C91-9E2B-143A0E222D37>