On 05/08/2018 05:47, Warren Young wrote:
It is not correct to say that Fossil had no output in this case. Its
output was the exit status code, which was zero, meaning there was no
failure.
I understand that it's too late now that some scripts would break if
diff/gdiff returned something like "N
On Aug 4, 2018, at 12:13 PM, Gilles wrote:
>
> But then, "fossil changes" returns nothing either, and it's coherent with the
> Unix philosophy.
Precisely. You’re applying Windows mores to a tool that comes out of the Unix
tradition. As long as you do that, you’ll have expectation mismatches.
On 04/08/2018 18:19, Stephan Beal wrote:
Outputting "no differences" to stdout would (IMO) be fine if
automation had the option to use --quiet to surprise that.
Considering no one thought about this before I mentioned that "fossil
diff" also returned nothing… it looks like it might not be that b
On Sat, Aug 4, 2018 at 5:31 PM Martin Gagnon wrote:
> Le sam. 4 août 2018 à 11:17, Stephan Beal a
> écrit :
>
>> If it was that common we would have realized the problem sooner ;).
>>
>> The problem with generating output for "no changes" is that we
>> potentially break any automation which reli
Le sam. 4 août 2018 à 11:17, Stephan Beal a écrit :
> If it was that common we would have realized the problem sooner ;).
>
> The problem with generating output for "no changes" is that we potentially
> break any automation which relies on an empty diff to mean "no changes".
>
That is what stder
If it was that common we would have realized the problem sooner ;).
The problem with generating output for "no changes" is that we potentially
break any automation which relies on an empty diff to mean "no changes".
(That lnly applies to "diff", not gdiff.) That could, i guess, be "fixed"
by addin
On 04/08/2018 16:43, Stephan Beal wrote:
That means there are no diffs to show. Try:
fossil gdiff --from prev test.html
That was it.
Grrr, I should have thought about it :-/
I don't know how common this mistake is, but if it, it might be a good
thing if Fossil said something like "No change.
On Sat, Aug 4, 2018 at 4:25 PM Gilles wrote:
> On 04/08/2018 15:51, Gilles wrote:
> > d:\Temp>fossil gdiff test.html
> >
> > Nothing.
>
> I don't know if it means anything, but incidently, "fossil diff" doesn't
> return anything either:
>
> d:\Temp>fossil diff test.html
>
> d:\Temp>fossil finfo t
On Sat, Aug 04, 2018 at 04:25:28PM +0200, Gilles wrote:
> On 04/08/2018 15:51, Gilles wrote:
> >d:\Temp>fossil gdiff test.html
> >
> >Nothing.
>
> I don't know if it means anything, but incidently, "fossil diff" doesn't
> return anything either:
>
> d:\Temp>fossil diff test.html
>
> d:\Temp>foss
On 04/08/2018 15:51, Gilles wrote:
d:\Temp>fossil gdiff test.html
Nothing.
I don't know if it means anything, but incidently, "fossil diff" doesn't
return anything either:
d:\Temp>fossil diff test.html
d:\Temp>fossil finfo test.html
History of test.html
2018-08-04 [6517de2577] Blah (user:
On 04/08/2018 15:36, Martin Gagnon wrote:
You can try to add "C:\Program Files\WinMerge" to your PATH
environment variable.
Then start a cmd window and try if it works by just typing winmergeu.
If it's works, this should works
fossil set gdiff-command winmergeu
fossil gdiff myfile.txt
On Sat, Aug 04, 2018 at 01:16:29PM +0200, Gilles wrote:
> Hello,
>
> I have a couple of questions:
>
> 1. Although fossil.exe is configured with…
>
> fossil settings > gdiff-command (global) "C:\Program
> Files\WinMerge\WinMergeU.exe"
>
> … nothing happens when I run "fossil gdiff myfile.txt
On 04/08/2018 15:17, Warren Young wrote:
On Aug 4, 2018, at 6:49 AM, Gilles wrote:
d:\temp\> fossil gdiff myfile.txt
Nothing.
Is d:\temp a checkout directory? What does “fossil stat” give in that
directory?
Yes. I used "d:\temp" to investigate this issue on a dummy repo.
d:\Temp>fossil s
On Aug 4, 2018, at 6:49 AM, Gilles wrote:
>
> d:\temp\> fossil gdiff myfile.txt
>
> Nothing.
Is d:\temp a checkout directory? What does “fossil stat” give in that
directory?
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://list
On 04/08/2018 14:10, Warren Young wrote:
Also, realize that Fossil will accept any unique prefix for
sub-commands. So, “fossil gd” is already a valid command: you don’t
need the TAB.
Thanks. Good enough.
___
fossil-users mailing list
fossil-users@lis
On 04/08/2018 14:07, Warren Young wrote:
Double check that the executable is in fact there, not somewhere else, like
c:\Program Files (x86).
If that doesn’t work, try “dir /x c:\” and putting in the short version of the
path to avoid the embedded space. If I had to guess, it’s:
c:\PROGR
On Sat, Aug 4, 2018 at 2:07 PM Warren Young wrote:
>
>
> https://hackaday.com/2018/01/19/linux-fu-custom-bash-command-completion/
There's one big caveat to doing so: trying to use features not explicitly
allowed for by the programmable completion will break completion in
annoying ways.
e.g. wh
On Aug 4, 2018, at 6:07 AM, Warren Young wrote:
>
>> fo + TAB : fossil.exe
>> fossil gd + TAB : fossil gdiff
>> fossil gdiff my + TAB :fossil gdiff myfile.txt
Also, realize that Fossil will accept any unique prefix for sub-commands. So,
“fossil gd” is already a valid command: you don’t need th
On Aug 4, 2018, at 5:16 AM, Gilles wrote:
>
> fossil settings > gdiff-command(global) "C:\Program
> Files\WinMerge\WinMergeU.exe”
Double check that the executable is in fact there, not somewhere else, like
c:\Program Files (x86).
If that doesn’t work, try “dir /x c:\” and putting in the s
Hello,
I have a couple of questions:
1. Although fossil.exe is configured with…
fossil settings > gdiff-command (global) "C:\Program
Files\WinMerge\WinMergeU.exe"
… nothing happens when I run "fossil gdiff myfile.txt".
Any idea what it could be? FWIW, I'm running Windows7.
2. Is there a
20 matches
Mail list logo
