2013/2/6 Stephan Beal :
> Fossil doesn't do any special
> interpretation of content other than to complain/warn if a file contains
> Windows-style newlines. (The newer UTF-related code has a similar check for
> invalid UTF, i believe.)
Currently, fossil only gives a warning when it encounters CR/N
Well, it is easier than that since I review the diffs in winmerge and
90% of the time I can ignore all diffs and commit.
And what does trickle through sticks out quite nicely.
Being a small development team, I only use a few fossil cmds and in a
tight flow.
fcom=fossil commit --user me
fpull=fossil
What about setting up diff-command to suit, then exporting the diff to
a patch file, fossil revert and then apply the patch?
On Wed, Feb 6, 2013 at 10:25 AM, wrote:
> Yes, I definitely have mixes of meaningful and non-meaningful [white
> space, case sensitive, empty lines] diffs to review.
> Whi
Yes, I definitely have mixes of meaningful and non-meaningful [white
space, case sensitive, empty lines] diffs to review.
While I would love to 'one-tool it' with fossil's diff tech, I find it
way easier to pop into winmerge and all its ignore goodies.
Maybe I'm too optimistic to expect that much p
So sounds like the problem you're trying to solve is that
* you have lots of *real* changes to a set of files
* most of those changes are meaningless in your environment
* so you're trying to separate the signal from the noise.
You can use fossil set diff-command 'diff -iw' to ignore case on the
d
Well, I agree, but the diff tools I use always have an 'ignore case' option.
Seems logical to me that would be an option in fossil also.
Unless text vs binary file assignments are super difficult?
While I prefer to seek the root of a problem, I cannot guarantee
syntax highlighting of source code.
On Wed, Feb 6, 2013 at 10:20 AM, wrote:
>
> The problem arises from code edits without syntax highlighting.
> So 'PI2' might be 'pi2' and fossil traps this as a diff.
>
Because it is a diff. 'p' and 'P' might mean the same thing in some
contexts, but that does not mean they are themselves the s
Ok,
Added a feature request after not finding similar request:
http://www.fossil-scm.org/index.html/tktview/c6afac6dee54d6658e66ed7b7ad8d5b18bd899a1
Thanks for fossil!
On Wed, Feb 6, 2013 at 10:30 AM, Stephan Beal wrote:
> On Wed, Feb 6, 2013 at 4:20 PM, wrote:
>>
>> Oh wow! Didn't realize ther
On Wed, Feb 6, 2013 at 4:20 PM, wrote:
> Oh wow! Didn't realize there was no global case-insensitive setting
> for file contents?
> The problem arises from code edits without syntax highlighting.
> So 'PI2' might be 'pi2' and fossil traps this as a diff.
>
There isn't one - that was a misunderst
Oh wow! Didn't realize there was no global case-insensitive setting
for file contents?
The problem arises from code edits without syntax highlighting.
So 'PI2' might be 'pi2' and fossil traps this as a diff.
Where do I edit globs for file contents?
"...with that possibility in mind, e.g. *.[fF][oO]
On Wed, Feb 6, 2013 at 7:50 AM, Themba Fletcher
wrote:
> It sounds like you're reporting that the file *contents* differ in
> case as opposed to the file names. If that's your report -- the
> case-sensitive flag only affects the file name comparisons:
>
A related point: the various glob settings
On Tue, Feb 5, 2013 at 6:56 PM, wrote:
> Hi,
> I noticed I am getting simple case sensitive differences despite
> having [ ] case-sensitive unchecked in local and remote repos?
> Anything else I need to do?
It sounds like you're reporting that the file *contents* differ in
case as opposed to the
Hi,
I noticed I am getting simple case sensitive differences despite
having [ ] case-sensitive unchecked in local and remote repos?
Anything else I need to do?
fossil version 1.25 [80bf94e0f7] 2013-01-18 21:34:21 UTC
Thanks for fossil!
___
fossil-users m
On Sat, Dec 22, 2012 at 1:02 PM, Stephan Beal wrote:
> i _think_ you could achieve what you're looking for by changing the glob to:
>
> *.[zZ][iI][pP],*.[pP][dD][fF],*.[hH][tT][mM]*
Yes, or simply use *.htm*,*.HTM*, because it's really unusual to have
mixed case extensions (at least in my setup)
On Tue, Dec 18, 2012 at 12:58 PM, Juanma Barranquero wrote:
> C:\work> fossil set ignore-glob
> ignore-glob (local) *.zip,*.pdf,*.htm*
>
i _think_ you could achieve what you're looking for by changing the glob to:
*.[zZ][iI][pP],*.[pP][dD][fF],*.[hH][tT][mM]*
Tedious, yes, but AFA
Hi.
It is a bug, or by design, that the ignore-glob does not honor the
setting of case-sensitive?
I haven't set case-sensitive, which means that on Windows defaults to false.
Then:
C:\work> fossil set ignore-glob
ignore-glob (local) *.zip,*.pdf,*.htm*
C:\work> fossil extras
o
16 matches
Mail list logo
