[fossil-users] 'diff --tk' of files within current dir only

Hello, is there an easy way to have 'diff --tk' display changes within a directory only (recursive or not)? (on today's trunk build, behaviour of 'diff *' works fine; however, 'diff --tk *' or 'diff --tk .' gives an error) Michai ___ fossil-users maili

[fossil-users] WAL mode vs other modes?

Hello, I recently noticed that if I hit /stat on my own repositories it shows ``delete mode'' in the Database Stats, but on www.fossil-scm.org it shows ``wal mode.'' I assume this is to leverage some of the benefits listed here: https://www.sqlite.org/draft/wal.html I suppose it can b

Re: [fossil-users] Merging two leaves not on the same graph?

Thus said Jan Nijtmans on Wed, 14 May 2014 12:11:42 +0200: > Anyway, I would like to execute the same plan (merge branch > "no-initial-commit" to trunk) once more. If anyone thinks this is a > bad idea (maybe because another bug prevents us to do that), I'm all > ears. I did

Re: [fossil-users] Excluding [brackets] from ... links

On Wed, May 14, 2014 at 10:59 PM, Joseph Prostko wrote: > suggested. In fact, I think I would prefer it. suggested = implemented I think I better head to sleep before I type anything else nonsensical today. I was going to come up with a patch for this, but I think I better call it a night bef

Re: [fossil-users] Excluding [brackets] from ... links

On Wed, May 14, 2014 at 10:10 PM, Andy Goth wrote: > On 5/14/2014 2:05 PM, Joseph Prostko wrote: >> I've encountered the problem you mentioned about highlighting, but >> admit I'm not sure if I'd like to see the brackets go away. > > I didn't suggest removing them from the display, only making th

Re: [fossil-users] Excluding [brackets] from ... links

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5/14/2014 2:05 PM, Joseph Prostko wrote: > I've encountered the problem you mentioned about highlighting, but > admit I'm not sure if I'd like to see the brackets go away. I didn't suggest removing them from the display, only making them be outsid

Re: [fossil-users] Excluding [brackets] from ... links

Thus said Matt Welland on Wed, 14 May 2014 16:08:50 -0700: > I have the same annoyance with scrape 'n paste. Would adding a space > between the "[" or "]" and the hex string alleviate the annoyance but > still provide the visual delineation? I think the problem isn't the amount of space bet

Re: [fossil-users] Excluding [brackets] from ... links

I have the same annoyance with scrape 'n paste. Would adding a space between the "[" or "]" and the hex string alleviate the annoyance but still provide the visual delineation? On Wed, May 14, 2014 at 2:58 PM, Joel Bruick wrote: > Stephan Beal wrote: > > On Wed, May 14, 2014 at 11:22 PM, B Har

Re: [fossil-users] Excluding [brackets] from ... links

Stephan Beal wrote: On Wed, May 14, 2014 at 11:22 PM, B Harder > wrote: Andy, to be clear, are you suggesting: a) blah blah [cafebabe] blah blah blah My comments assumed this interpretation. To my eyes that looks a tiny bit cleaner, but i won't argue s

Re: [fossil-users] Excluding [brackets] from ... links

That's what I was imagining/hoping too, but I'm not sure if that was original proposal. I like the way the "[" "]" set off the string we care about, but then I wondered if the ease of select/copy was because the brackets were completely eliminated. -bch On 5/14/14, Stephan Beal wrote: > On Wed,

Re: [fossil-users] Excluding [brackets] from ... links

On Wed, May 14, 2014 at 11:22 PM, B Harder wrote: > Andy, to be clear, are you suggesting: > > a) blah blah [cafebabe] blah blah blah > My comments assumed this interpretation. To my eyes that looks a tiny bit cleaner, but i won't argue strongly one way or the other. -- - stephan beal ht

Re: [fossil-users] Excluding [brackets] from ... links

Andy, to be clear, are you suggesting: a) blah blah [cafebabe] blah blah blah b) blah blah cafebabe blah blah blah ? -bch On 5/14/14, Joseph Prostko wrote: > On Wed, May 14, 2014 at 2:38 PM, Andy Goth wrote: >> I'd like for the [bracket] characters to not be part of the ... >> links >>

Re: [fossil-users] Excluding [brackets] from ... links

On Wed, May 14, 2014 at 2:38 PM, Andy Goth wrote: > I'd like for the [bracket] characters to not be part of the ... links > in Fossil web pages, at least when the link text is an artifact ID. This > change would make it easier to highlight just the artifact ID and omit the > brackets so that I ca

Re: [fossil-users] Excluding [brackets] from ... links

On Wed, May 14, 2014 at 8:38 PM, Andy Goth wrote: > elsewhere without having to then delete the brackets manually. Most web > browsers make it very hard to start highlighting in the middle of link > text, as they choose to interpret that as dragging an object. > > Any thoughts? i think it just

[fossil-users] Excluding [brackets] from ... links

I'd like for the [bracket] characters to not be part of the ... links in Fossil web pages, at least when the link text is an artifact ID. This change would make it easier to highlight just the artifact ID and omit the brackets so that I can paste it elsewhere without having to then delete the

Re: [fossil-users] Changing file name and creating old file name at same time causes potential problem

Thus said Stephan Beal on Wed, 14 May 2014 17:47:43 +0200: > 'mv' (for reasons ido not understand) sets > vfile.origname=vfile.pathname where vfile.origname IS NULL (that > caused me a bit of greif in libfossil, as i have to work around it in > several places).

Re: [fossil-users] committing wiki pages changes format parser

On Wed, May 14, 2014 at 6:33 PM, Stephan Beal wrote: > i need to test this a bit more before committing, and would like to > consider adding a filter which rejects any unknown mime types (but i'm not > sure that's such a good idea because i have uses for non-canon mime types > via the JSON API...

Re: [fossil-users] committing wiki pages changes format parser

On Wed, May 14, 2014 at 5:55 PM, Stephan Beal wrote: > Would this strategy server your purpose: > > - add a (-format FORMAT) option to (wiki commit). > > - if no format is specified, use the format from the prior version (if > there is one), defaulting to fossil-wiki if no prior version is set or

Re: [fossil-users] committing wiki pages changes format parser

On Tue, May 13, 2014 at 9:27 PM, Chad Perrin wrote: > On Tue, May 13, 2014 at 09:55:10AM +0200, Stephan Beal wrote: > > Doh - you can't currently. The shell mode export/import was added _long_ > > before other formats were supported, and it's not aware of them. i've > added > > that to the TODO l

Re: [fossil-users] Changing file name and creating old file name at same time causes potential problem

On Wed, May 14, 2014 at 2:43 AM, Andy Bradford wrote: > Indeed it didn't include foo.txt, so it silently removed > foo.txt from the checkin. It picked up the rename from > 03764343bf2b76127272b251db39498f61ac31c1 and it should have included the > foo.txt from the

Re: [fossil-users] Merging two leaves not on the same graph?

2014-05-08 19:26 GMT+02:00 Stephan Beal : > It's funny you say that because in libfossil i've had to go back and > reexamine my 0 semantics, and let them be legal (empty repo) in some cases, > but stand for the current checkout in others (where 0 otherwise makes no > sense). Negatives are always in