On Sun, Dec 7, 2014 at 12:35 PM, Stephan Beal wrote:
> On Sun, Dec 7, 2014 at 6:55 PM, wrote:
>>
>> The problem: A (mostly) text file with just a few normally non-text chars
>> which confuse fossil into thinking the whole file is binary.
>
>
> There's an irony in there somewhere. It can't be part
Thus said Richard Hipp on Mon, 08 Dec 2014 15:28:30 -0500:
> So what is the point of this? Why is the default text/binary detection
> not working for Tony?
And more specifically (I didn't know about this command until Stephen
showed it):
$ fossil test-looks-like-utf 9s08gw32.s8p
File "9s08gw
On 12/7/2014 10:35 AM, Andy Bradford wrote:
I downloaded your zip file and looked at the
files and discovered that the last few bytes of each file has some
control characters (0x1a, 0x1d), null characters (0x00) and one has an
extended ASCII character 0xe6.
$ od -x 9s08gw32.s8p |
Thus said Richard Hipp on Mon, 08 Dec 2014 15:28:30 -0500:
> So what is the point of this? Why is the default text/binary detection
> not working for Tony?
I looked at the two files he sent as an example, and they had a null
byte (0x00) at the end of the file.
Andy
--
TAI64 timestamp: 40
ay, December 08, 2014 11:09 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] How to force text for all files?
On Mon, Dec 08, 2014 at 03:28:30PM -0500, Richard Hipp wrote:
On Mon, Dec 8, 2014 at 3:22 PM, bch wrote:
Does the "mode" (text/binary) factor into the sha1
On Mon, Dec 08, 2014 at 03:28:30PM -0500, Richard Hipp wrote:
>
>
> On Mon, Dec 8, 2014 at 3:22 PM, bch wrote:
>
> Does the "mode" (text/binary) factor into the sha1 fingerprint hash of
> an artifact (single file) or commit ?
>
>
>
> No. The "mode" is only used to determine how t
On Mon, Dec 8, 2014 at 9:09 PM, Shal Farley wrote:
> I would disagree with part of this statement. I agree that ASCII defines
> only the 7-bit code values, but I think this whole thread has run off the
> rails in talking about the content values as determining whether the file
> is "text" or "bin
On Mon, Dec 8, 2014 at 3:22 PM, bch wrote:
> Does the "mode" (text/binary) factor into the sha1 fingerprint hash of
> an artifact (single file) or commit ?
>
>
No. The "mode" is only used to determine how to display the content on a
webpage. Also, independent changes can only be merged in text
Does the "mode" (text/binary) factor into the sha1 fingerprint hash of
an artifact (single file) or commit ?
-bch
On 12/8/14, Martin Gagnon wrote:
> On Mon, Dec 08, 2014 at 12:09:57PM -0800, Shal Farley wrote:
>> Stephan,
>>
>> > If it has ANY bytes above 127, it's not, by definition, ASCII. i.
On Mon, Dec 08, 2014 at 12:09:57PM -0800, Shal Farley wrote:
> Stephan,
>
> > If it has ANY bytes above 127, it's not, by definition, ASCII. i.e.
> > "it's binary."
>
> I would disagree with part of this statement. I agree that ASCII
> defines only the 7-bit code values, but I think this whole th
Stephan,
> If it has ANY bytes above 127, it's not, by definition, ASCII. i.e.
> "it's binary."
I would disagree with part of this statement. I agree that ASCII defines
only the 7-bit code values, but I think this whole thread has run off
the rails in talking about the content values as determ
On Sun, Dec 7, 2014 at 8:02 PM, wrote:
> I could claim that a file containing all 256 ASCII codes is a text file
> for my use. On the contrary I could also
>
That's the thing: there AREN'T 256 ASCII points. ASCII defines only 7, with
the 8th being being used by applications back in the day. e
wrote:
> -Original Message-
> From: Will Parsons
>
>>And how could one possibly distinguish a file containing all 256 byte
>> bit patterns from a binary file?
>
> That's the point, in effect you can't. It's up to you to decide how to
> interpret a file.
>
>>Referring to "all 256 ASCII c
-Original Message-
From: Will Parsons
And how could one possibly distinguish a file containing all 256 byte
bit patterns from a binary file?
That's the point, in effect you can't. It's up to you to decide how to
interpret a file.
Referring to "all 256 ASCII codes" is a misnomer.
wrote:
> This is a multi-part message in MIME format.
>
> --===0379594130==
> Content-Type: multipart/alternative;
> boundary="=_NextPart_000_001C_01D01261.2A93EE90"
>
> This is a multi-part message in MIME format.
>
> --=_NextPart_000_001C_01D01261.2A93EE90
> Content-Typ
Hit Tony,
On 7 December 2014 at 09:55, wrote:
> I'm not sure about the exact characters that may be causing this as each
> file has different ones. (What characters would make the file binary in
> fossil’s eyes?)
>
> I'm dropping a zip with two examples here
> (www.dropbox.com/s/bmjp65hfcv1ex9w/
ssion
Subject: Re: [fossil-users] How to force text for all files?
On Sun, Dec 7, 2014 at 6:55 PM, wrote:
The problem: A (mostly) text file with just a few normally non-text chars
which confuse fossil into thinking the whole file is binary.
There's an irony in there somewhere. It can&#
On Sun, Dec 7, 2014 at 6:55 PM, wrote:
> The problem: A (mostly) text file with just a few normally non-text
> chars which confuse fossil into thinking the whole file is binary.
>
There's an irony in there somewhere. It can't be partly binary, it is
either entirely binary or not binary. i.e. 0
Thus said to...@acm.org on Sun, 07 Dec 2014 19:55:46 +0200:
> I'm not sure about the exact characters that may be causing this as
> each file has different ones. (What characters would make the file
> binary in fossil's eyes?)
Without actually looking at the source code, I suspect it tre
are small.
The real problem is that once a file is treated as binary I can not ‘diff’ it
between versions.
Thanks.
-Original Message-
From: Andy Bradford
Sent: Sunday, December 07, 2014 3:32 AM
To: to...@acm.org
Cc: Fossil SCM user's discussion
Subject: Re: [fossil-users] How t
Thus said to...@acm.org on Sat, 06 Dec 2014 22:23:33 +0200:
> One common (for me) example is a text file that includes maybe just
> one or two special 8-bit ASCII codes. This causes the whole files to
> be stored as binary and makes it impossible to `diff'.
I committed some files with è (wh
ssion
Subject: Re: [fossil-users] How to force text for all files?
On Sat, Dec 6, 2014 at 3:12 PM, wrote:
Hi,
I’m looking for a way to force all files (except those matching binary-glob)
to be treated as text rather than automatically (mis-)detected as binary.
Can you share with us what
On Sat, Dec 6, 2014 at 3:12 PM, wrote:
> Hi,
>
> I’m looking for a way to force all files (except those matching
> binary-glob) to be treated as text rather than automatically (mis-)detected
> as binary.
>
>
>
Can you share with us what it is about your files that cause them to be
misdetected a
Hi,
I’m looking for a way to force all files (except those matching binary-glob) to
be treated as text rather than automatically (mis-)detected as binary.
Any way to do that?
TIA___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://li
24 matches
Mail list logo
