On Sun, May 21, 2023 at 03:42:19PM -0400, James Cook wrote:
> On May 18, 2023 3:16:34 p.m. EDT, Omar Polo <op@omarpolo.com> wrote:
> >On 2023/05/18 11:08:54 +0200, NilsOla Nilsson <nilsola@abc.se> wrote:
> >> On Wed, May 17, 2023 at 07:03:22PM +0200, Omar Polo wrote:
> >> >
> >> > still in doubt if it's useful to waste spaces on the mirrors for a
> >> > debug package for this.
> >>
> >> There is also dwdiff in ports, which is probably
> >> better. From the manpage:
> >> dwdiff is mostly command-line compatible with wdiff
> >
> >I've missed that, thanks!
> >
> >I couldn't make it highlight the difference as wdiff does without "|
> >less" but it's not a big deal, and more importantly it doesn't crash
> >out of the box!
> >
> >At this point I'm wondering whether we should remove wdiff and just
> >point users to dwdiff...
> >
>
> I have not tried dwdiff, but if it can't highlight differences in less output, I would definitely miss that feature. I find it hard to see where the differences are unless they stand out like that; otherwise it's just a jumble of text.
> --
> James
dwdiff seems to have this feature: I just tried it briefly, but it looks
like
got diff | dwdiff -ul | less
is a replacement for
got diff | wdiff -ad
or
got diff | wdiff -dl | less
So my first impression is I won't miss wdiff. Thanks Nils!
--
James
No comments:
Post a Comment