[fossil-users] Minor typos in fossil documentation

The fossil documentation is so good, it's a shame to allow even the tiniest imperfection! 1. https://www.fossil-scm.org/xfer/doc/trunk/www/private.wiki "clone, sync, or scrub and individual private branch" should be "clone, sync, or scrub an individual private branch" 2.

Re: [fossil-users] Feature request: local .fossil-ignore

@Barry: True, but it's clumsy, since you have to specify every path, in full, in the global ignore-glob file. If you move a subproject to a different location in the directory tree, you have to remember to update the ignore-glob file. This is something I miss from Subversion (and Git, too,

Re: [fossil-users] Non empty directories

Dan, if I've understood correctly, 'fossil addremove' should do what you want. Here's an example from a freshly created repo (fossil 2.1) with no files currently added: http://pastebin.com/9TzyXbd6 Can you post a similar output to show what you're observing? On Wed, Mar 15, 2017, at

Re: [fossil-users] Using Fossil SCM with Master Repositories held on aFlash Drive ?

Hi Martin, One disadvantage of copying repositories between the thumb drive and your client's PC is that there's a risk of accidentally overwriting a newer repository with an older one. Unlikely, of course, but if it did happen, you'd permanently lose data. Another drawback is that if you

Re: [fossil-users] db errors after Ctrl-C

Unfortunately, the bug is a proper Heisenbug, and refuses to manifest at all under the debugger. I read up on the behaviour of Ctrl-C under Windows, here: https://msdn.microsoft.com/en-us/library/windows/desktop/ms682541%28v=vs.85%29.aspx and it's supposed to work like this: 1) If no handler is

Re: [fossil-users] db errors after Ctrl-C

OK, I tried installing an interrupt handler that ignores the interrupt. This fixes my original problem, but of course means that you can never interrupt a long-running operation! Not really viable. It looks to me like main() needs an interrupt handler that works like shell's: sets some kind of

Re: [fossil-users] db errors after Ctrl-C

I think shell.c is used for "fossil sqlite3" mode, not for what I'm doing. For normal operations, the main() in main.c is invoked, and that main() doesn't install any kind of interrupt handler. It looks to me like main.c needs to install a sigint handler, like shell.c does. I'm going to

[fossil-users] db errors after Ctrl-C

I noticed a minor bug in fossil. Observed on Windows 10 with all of: 1) fossil 1.35 and 1.36 (downloaded executables): 2) built from source (MSVC build, latest code as of 2016-12-11) I am in the open checkout of a local (file) repository. I have added a large number of files. Some have mixed line

Re: [fossil-users] how to report bug in fossil

Thanks! That patch works for me. Ross On Fri, Jun 10, 2016, at 10:01 AM, Scott Robison wrote: > On Thu, Jun 9, 2016 at 2:12 PM, Warren Young wrote: >> On Jun 9, 2016, at 6:25 AM, rosscann...@fastmail.com wrote: >> > >> > The bug: >> > In lookslike.c, invalid_utf8()

Re: [fossil-users] how to report bug in fossil

I'm new to this list, so take my opinion lightly, but I would hesitate to introduce Boost into the fossil build if it's not there already. Boost adds a long list of complications to any build it's part of: - it's massive; - it has dependencies between its modules, so even if you just want a tiny

[fossil-users] how to report bug in fossil

Hi, I've found what seems to be a minor bug in fossil (details below), and I'm not sure what the procedure is for reporting it. Can someone enlighten me? The bug: In lookslike.c, invalid_utf8() returns 'invalid' for the input 0xE0, 0xB8, 0x94, which is the Thai character 'do dek' (U+0E14). This