Hello,
I noticed 'fossil diff .' or 'fossil diff *' in a subdir of the
working tree does not work (i.e. produces an error from fossil).
Apart from using shell magic, is there a way to restrict 'diff' to use
a single dir (e.g. the current one)?
Not a big deal, but perhaps there's a short answer.
Date: Tue, 8 Jul 2014 16:03:27 +0200
From: Michai Ramakers m.ramak...@gmail.com
To: Fossil SCM user's discussion fossil-users@lists.fossil-scm.org
Subject: [fossil-users] diff restricted to a dir
Message-ID:
cadefdofyphaesfb0c-fsqzbj7p6cgyfsdeqzaevkxtp6aaq...@mail.gmail.com
On 8 July 2014 18:09, Tomek Kott tkott.onl...@outlook.com wrote:
Date: Tue, 8 Jul 2014 16:03:27 +0200
From: Michai Ramakers m.ramak...@gmail.com
To: Fossil SCM user's discussion fossil-users@lists.fossil-scm.org
Subject: [fossil-users] diff restricted to a dir
Message-ID:
On Tue, Jul 8, 2014 at 7:01 PM, Michai Ramakers m.ramak...@gmail.com
wrote:
On 8 July 2014 18:09, Tomek Kott tkott.onl...@outlook.com wrote:
fossil ls DIR/ | fossil diff
that worked for me.
Basically pipe the output of what fossil knows about the directory to the
differ
Thanks, but
On 8 July 2014 20:22, Stephan Beal sgb...@googlemail.com wrote:
On Tue, Jul 8, 2014 at 7:01 PM, Michai Ramakers m.ramak...@gmail.com
wrote:
On 8 July 2014 18:09, Tomek Kott tkott.onl...@outlook.com wrote:
fossil ls DIR/ | fossil diff
that worked for me.
Basically pipe the output of
Hello,
I have some Tcl scripts (for IRC) that previously had no problems when I
committed. They don't have UTF-8 characters at all, but when I try to
commit them I get the warning:
./test.tcl contains invalid UTF-8. Use --no-warnings or the encoding-glob
setting to disable this warning.
2014-07-08 20:47 GMT+02:00 Andy Bradford amb-fos...@bradfords.org:
Hello,
I have some Tcl scripts (for IRC) that previously had no problems when I
committed. They don't have UTF-8 characters at all, but when I try to
commit them I get the warning:
./test.tcl contains invalid UTF-8. Use
On Tue, Jul 8, 2014 at 8:47 PM, Andy Bradford amb-fos...@bradfords.org
wrote:
If I remove the the è (0xe8) character I can commit.
I didn't think 0xe8 was UTF-8, but maybe I'm mistaken?
No characters between 128 and 255 are valid UTF-8, to avoid confusion with
the many encodings which use
On Tue, Jul 8, 2014 at 8:28 PM, Michai Ramakers m.ramak...@gmail.com
wrote:
fossil diff $(fossil ls DIR/)
right, that works, ok. (Not on windows, but then again, since nobody
asked before, I am guessing nobody really uses diff-in-one-dir-only a
lot.)
Had never occurred to me until today,
Message: 8
Date: Tue, 8 Jul 2014 21:40:22 +0200
From: Stephan Beal sgb...@googlemail.com
To: Fossil SCM user's discussion fossil-users@lists.fossil-scm.org
Subject: Re: [fossil-users] diff restricted to a dir
Message-ID:
Thus said Jan Nijtmans on Tue, 08 Jul 2014 21:35:07 +0200:
If you don't want this warning, just set 'encoding-glob' to '*'.
I might actually want encoding warnings though...
But did you ever view this file in the fossil UI?
Did the è really look like è there?
I did not, however, if I
Thus said Stephan Beal on Tue, 08 Jul 2014 21:37:50 +0200:
No characters between 128 and 255 are valid UTF-8, to avoid confusion
with the many encodings which use that range.
If no characters between 128 and 255 are valid UTF-8, and they can never
be valid UTF-8 characters, and are used by
On Tue, Jul 8, 2014 at 3:38 PM, Andy Bradford amb-fos...@bradfords.org
wrote:
That's a good suggestion for fixing the Tcl script, but I'm still not
sure why Fossil thinks that è is UTF-8. I thought it was extended ASCII.
I didn't think 0xe8 was UTF-8, but maybe I'm mistaken?
In the
Interesting question/option, but i have no answer. Something to possibly
consider?
(sent from a mobile device - please excuse brevity, typos, and top-posting)
- stephan beal
http://wanderinghorse.net
On Jul 8, 2014 11:43 PM, Andy Bradford amb-fos...@bradfords.org wrote:
Thus said Stephan
Thus said Scott Robison on Tue, 08 Jul 2014 15:48:05 -0600:
The warning you are seeing is that the stream is invalid UTF-8. 0xE8
byte could be an extended ASCII character from one of the ISO-8859-X
code pages. Or it could be real binary data that just happens to
mostly have ASCII text
Andy,
If no characters between 128 and 255 are valid UTF-8, and they can
never be valid UTF-8 characters, and are used by many encodings,
why doesn't Fossil simply ignore them when they are committed?
I think Stephan said it poorly. A solitary byte in that range is never
valid UTF-8, but
Thus said Stephan Beal on Tue, 08 Jul 2014 23:50:40 +0200:
Interesting question/option, but i have no answer. Something to
possibly consider?
Or perhaps just making the documentation more clear that all files must
be valid UTF-8. There is already an option to control how encodings are
17 matches
Mail list logo