Hello,
I'm working on a simple course - using markdown markup for text files
and store few pdf files.
I changed settings for 'diff' command to 'meld', but then reverted back
to use built-in diff for 'diff' command and 'meld for gdiff/gmerge.
However, Fossil is now complaining...
See the output:
On Sat, Jul 26, 2014 at 12:26 PM, Gour wrote:
> $ fossil chan
> EDITED 2.md
> $ fossil diff
> (it launches meld here)
> $ fossil settings
> gdiff-command(local) meld
>
Weird. i can't reproduce that on my system:
[stephan@host:~/cvs/fossil/fossil]$ f set gdiff
gdiff-command(
Stephan Beal writes:
> This probably won't help, as your ls listing shows us that file doesn't
> exist, but can you try:
>
> rm '/home/gour/prj/iching/2.md~0'
Of course,
rm: cannot remove ‘/home/gour/prj/iching/2.md~0’: No such file or
directory
> What platform is this?
Linux x86_64 Debian (S
On 26 July 2014 12:26, Gour wrote:
> Hello,
>
> I'm working on a simple course - using markdown markup for text files
> and store few pdf files.
>
> I changed settings for 'diff' command to 'meld', but then reverted back
> to use built-in diff for 'diff' command and 'meld for gdiff/gmerge.
>
> How
On Sat, Jul 26, 2014 at 1:03 PM, Michai Ramakers
wrote:
> I can reproduce it here when setting 'diff-command' to the empty
> string. Perhaps you have done that too (from the looks of 'fossil set'
> output).
>
> You can unset an option using 'fossil unset'.
>
Good catch!
Does fossil need to alwa
Michai Ramakers
writes:
> I can reproduce it here when setting 'diff-command' to the empty
> string. Perhaps you have done that too (from the looks of 'fossil set'
> output).
Good catch. ;)
Yes, I wanted to 'unset' it via ui command.
> You can unset an option using 'fossil unset'.
Thanks.
Ma
I'm starting a company with some folks. Their notion of the default choice
for SCM is git + JIRA for bug tracking + some other tool we'd pick for code
review. This is probably quite common. Since the answers to my questions
will probably be interesting to a relatively wide audience, I hope the
f
On Sat, Jul 26, 2014 at 10:53 AM, Eric Rubin-Smith
wrote:
>
> * Export of tickets.
>
> If we want to move away from fossil to a git-based thing in the future, we
> can export the source version history, though that is not as trivial as the
> Fossil page on the matter makes it seem (see below).
>
Thus said Gour on Sat, 26 Jul 2014 13:18:59 +0200:
> Maybe fossil's ui should be able to do the same?
It can. Run ``fossil ui'' and browse to Admin->Settings
Andy
--
TAI64 timestamp: 400053d3ce0e
___
fossil-users mailing list
fossil-users@lists
"Andy Bradford"
writes:
> It can. Run ``fossil ui'' and browse to Admin->Settings
Well, the error is result of applying 'fossil ui' on diff-command
settting. ;)
Sincerely,
Gour
--
Before giving up this present body, if one is able to tolerate
the urges of the material senses and check the
On 26 July 2014 18:53, Gour wrote:
> "Andy Bradford"
> writes:
>
>> It can. Run ``fossil ui'' and browse to Admin->Settings
>
> Well, the error is result of applying 'fossil ui' on diff-command
> settting. ;)
The issue here is that you cannot unset a variable through the UI; you
can only set it
Michai Ramakers
writes:
> The issue here is that you cannot unset a variable through the UI; you
> can only set it to the empty string, right?
Correct...and that produces error as demonstrated here.
Sincerely,
Gour
--
As a lamp in a windless place does not waver, so the transcendentalist,
w
Quotable:
I must say that Fossil is the best thing to happen
to my development workflow this year, as I am pretty sure that using
Git has resulted in the premature death of too many of my brain cells.
I'm glad to be able to replace Git in every place that I possibly can
with Fossil.
On Jul 25, 201
I'm on mobile device - please excuse typos/brevity.
I managed a team of about 10 local committers (in my office) and about 10
more remote (across the country).
I had a FreeBSD production environment. I setup a FreeBSD dev/testing
environment where everybody was isolated by jails, and had their ow
On Fri, Jul 25, 2014 at 11:08 PM, Joe Prostko wrote:
> Using the handy `fossil bisect`, I found that this revision is causing
> me problems while compiling Fossil from within Haiku.
I did some more digging, and the problem seems to be that the assert.h
included from within config.h is causing pro
Richard Hipp wrote:
> Is there a better story for moving between any two bug tracking
> systems? Do there exist any two bug tracking systems in the world were
> you can move from one to the other without having to write some scripts to
> transform the data?
I can't tell whether you're aski
16 matches
Mail list logo
