Keepun wrote:
Files with encoding greater than 8 bits without BOM at the beginning can be
immediately identified as binary.
No, the BOM is not required or recommended in UTF-8, so it would be a mistake to
identify GNU/Linux text files as binary merely because they lack a BOM.
Typically these
Hi,
How to reproduce:
Scenario:
|dirA .. bar -> foo foo dirB .. |
Diff man
|-N, --new-file treat absent files as empty --no-dereference don't follow
symbolic links |
Output
|$ diff --no-dereference dirA dirB > /dev/null $ diff -N --no-dereference
dirA dirB > /dev/null diff: dirB/bar: No
On 04/17/2018 07:17 AM, Alessandro wrote:
It's seems a bug, any fix or workaround for that?
I don't see a bug. "Don't follow symbolic links" doesn't mean "Pretend
symbolic links do not exist".
On 04/17/2018 11:28 AM, Alessandro wrote:
The bug is why show the error and ignore -N on sym link.
I think we are miscommunicating. What I am saying is that diff is not
ignoring -N, and there is an error if one directory has a dangling
symlink and another directory has nothing.
Hi,
The bug is why show the error and ignore -N on sym link.
Thx
(+ML)
On 17/04/2018 17:57, Paul Eggert wrote:
On 04/17/2018 07:17 AM, Alessandro wrote:
It's seems a bug, any fix or workaround for that?
I don't see a bug. "Don't follow symbolic links" doesn't mean "Pretend
symbolic
Yep i know but i need to use -N on my scenario.
On 17/04/2018 22:49, Paul Eggert wrote:
On 04/17/2018 01:34 PM, Alessandro wrote:
So, how we can solve it?
Perhaps 'diff' should not report an error in this situation if -N is
specified.
UTF-8 does not require BOM, but for UTF-16 and UTF-32 BOM is always
present. Files with UTF-16 and UTF-32 without the BOM should be
identified as binary.
But why there are no plans to support UTF-16 and UTF-32? Diff is part of
the Git and is used all over the world. Now 2018 and Unicode
On 04/17/2018 01:27 PM, Keepun wrote:
why there are no plans to support UTF-16 and UTF-32?
Nobody has volunteered to do it, and there hasn't been a pressing need.
UTF-16 and UTF-32 are primarily used for internal representation, not
for text files. For more on the subject, please see:
So, how we can solve it?
On 17/04/2018 22:12, Paul Eggert wrote:
On 04/17/2018 11:28 AM, Alessandro wrote:
The bug is why show the error and ignore -N on sym link.
I think we are miscommunicating. What I am saying is that diff is not
ignoring -N, and there is an error if one directory has
On 04/17/2018 01:34 PM, Alessandro wrote:
So, how we can solve it?
Perhaps 'diff' should not report an error in this situation if -N is
specified.
10 matches
Mail list logo
