Re: [fossil-users] Quiet mode for update and sync
Thus said David Mason on Sun, 05 Oct 2014 11:05:27 -0400: + if ( statusFlag ) fossil_exit(nUpdate==0); } Before you start using this in your own fork, you might want to consider if having the update_cmd() function exit at this point will cause problems if FOSSIL_ENABLE_TH1_HOOKS is enabled when using statusFlag and there are no updates. I don't use FOSSIL_ENABLE_TH1_HOOKS (and maybe you don't either), but one side effect of causing update_cmd() to exit here means that FOSSIL_ENABLE_TH1_HOOKS code in main.c will not execute. Not sure if that is an issue. Someone who knows more about the #ifdef FOSSIL_ENABLE_TH1_HOOKS in main.c will likely know more: http://www.fossil-scm.org/index.html/info/394258fc8108f16ca99a8bac1a04fab209d53e7d?ln=757,765 I would look at other fossil subcommands to see if any of them exit (except those that call fossil_fatal co. or exit with an error); my cursory glance seems to indicate that most fossil subcommands do not exit except for errors. I suppose perhaps the current intention is to have it exit with with a non-zero (aka error) exit status if nUpdate==0 so perhaps this is not such a bad change, but it does warrant some consideration for the case where it will exit without an error. At the moment, nUpdate==0 will always cause fossil to exit non-zero because it doesn't actually sync, so nUpdate would only ever be 0 if you gave it a name to which Fossil can actually update, but it wouldn't mean that you have new sync content, only that there are changes possible from your current checkout to the new checkout requested. Thanks, Andy -- TAI64 timestamp: 4000543239e2 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] move many files
Hi, What is the easiest way to move many files in fossil on windows? 1) dir Directory of F:\dev2\fossil-experiment\tinymce 06-Oct-14 15:41DIR . 06-Oct-14 15:41DIR .. 06-Oct-14 14:54DIR javascript 06-Oct-14 14:34DIR tinymce 06-Oct-14 14:34 2 testfile.txt 2) fossil changes -v (none) 3) \tinymce has : 282 File(s) 341 Dir(s) 4) I want to move \tinymce to javascript\tinymce. So do I need to write some kind of script that : fires fossil ls filters that output to consider only files inside \tinymce (ie ignore testfile.txt) and then fires fossil rename on that output ? Thanks. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Is it possible to add empty folders to the repo?
I tried doing: mkdir a fossil add a but that didn't work. -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Is it possible to add empty folders to the repo?
Nope - fossil tracks files only. - stephan Sent from a mobile device, possibly from bed. Please excuse brevity and typos. On Oct 6, 2014 4:38 PM, Baruch Burstein bmburst...@gmail.com wrote: I tried doing: mkdir a fossil add a but that didn't work. -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Is it possible to add empty folders to the repo?
On Mon, Oct 06, 2014 at 04:44:30PM +0200, Stephan Beal wrote: Nope - fossil tracks files only. But you can always add a .keep file or something in a directory you want to keep around and track that. - stephan Sent from a mobile device, possibly from bed. Please excuse brevity and typos. On Oct 6, 2014 4:38 PM, Baruch Burstein bmburst...@gmail.com wrote: I tried doing: mkdir a fossil add a but that didn't work. -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı -- James Turner ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Is it possible to add empty folders to the repo?
maybe you could use : fossil settings empty-dirs A comma or newline-separated list of pathnames. On update and checkout commands, if no file or directory exists with that name, an empty directory will be created. On Mon, Oct 6, 2014 at 8:07 PM, Baruch Burstein bmburst...@gmail.com wrote: I tried doing: mkdir a fossil add a but that didn't work. -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Is it possible to add empty folders to the repo?
Arguably, if you need empty dirs in your project as part of a build process, it should be in the Makefile or equiv. -bch On 10/6/14, Gaurav M. Bhandarkar gaurav.a...@gmail.com wrote: maybe you could use : fossil settings empty-dirs A comma or newline-separated list of pathnames. On update and checkout commands, if no file or directory exists with that name, an empty directory will be created. On Mon, Oct 6, 2014 at 8:07 PM, Baruch Burstein bmburst...@gmail.com wrote: I tried doing: mkdir a fossil add a but that didn't work. -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Is it possible to add empty folders to the repo?
Fossil only tracks files. So in order to create a directory you must have at least one file in that directory. On Mon, Oct 6, 2014 at 10:37 AM, Baruch Burstein bmburst...@gmail.com wrote: I tried doing: mkdir a fossil add a but that didn't work. -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Is it possible to add empty folders to the repo?
Just for the record: I was not looking for a way to do this. I am trying to work on a svn-import command, and since svn allows this, I just wanted to make sure that I was right in thinking fossil does not allow it, and empty dirs will not get imported. -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Is it possible to add empty folders to the repo?
On Mon, Oct 6, 2014 at 4:47 PM, Gaurav M. Bhandarkar gaurav.a...@gmail.com wrote: maybe you could use : fossil settings empty-dirs Nice tip :). i've been using Fossil since Christmas of 2007 and still learning new things about it. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Cloning repo
On Mon, Oct 6, 2014 at 6:24 AM, Andy Bradford amb-fos...@bradfords.org wrote: After looking at it, I don't think this introduces any unwanted side effects. :-D autosync-tries dictates how many times ``autosync'' should ...autosync-tries would be honored and one would have to enter the password for a maximum of 2 * autosync-tries. That's what it looked like to me. Potentially annoying but harmless (and abortable with a Ctrl-C). Maybe if we could distinguish between password failure and other Seems to me to be rare corner case which isn't necessary. Maybe in certain setups/uses, but i can't say i'd ever conceived of this problem until Jacek (the OP) posted it. For the archives, here is what happens when I have autosync-tries set to 2 and a password failure: ... Autosync failed. continue in spite of sync failure (y/N)? n $ Seems to behave as I would expect. Any other opinions? Agreed. No less surprising result for that case comes to mind. But now that you mention autosync retry count... i'm not 100% sure i put that ++nErrs in the right place: http://www.fossil-scm.org/index.html/info/165cc5c093e6ee36a78de5e01f7049235dbc1b1c?ln=1856-1867 Could i convince you to give that look? -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Captcha and blind and visually impaired users
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Legend has it that on 05/10/2014 19:47, the fair wind whisper'd the words of Stephan Beal: Agreed completely, but most people, i assume, who are contributing to the wiki and tickets are capable of entering a captcha? Yes, the keyword here being most. Visually impaired people are unfortunately an exception. To be clear: i'm not saying no, we can't, i'm just voicing concern for automated repo pollution which such a combination creates. I see your concern and would certainly like to avoid spam just as much, thus I completely agree with what you wrote. My concern is that at the moment blind and visually impaired people are unable to contribute to any repository where registration is enabled with equal access rights (due to the required captcha). What I am requesting might not be perfect (hence it should be toggleable), but it would be a step forward compared to what we have now. If anyone could implement a textual captcha that asks for a word or the sum of numbers, then we would have a perfect solution. I feel though that this is perhaps a bit too much to ask. A moderation step is essentially the same thing registration via email to the admin, but arguably requiring less effort on the admin's part (checking the timeline page periodically for pending moderation requests, and clicking accept/deny for each requests). Exactly. Email-based moderation on the other hand might not be a viable option, as Fossil, to my knowledge, does not contain any feature that would allow sending emails. But do you want robots to be included in those tickets? i once had a repo where the anonymous user had (due to an error on my part) privileges which allowed him to edit wiki pages and create tickets. Over a span of a few weeks, it injected dozens of entries via the anonymous account (where autocaptcha was active). It remained undetected because it was clever enough to know not to edit the configured home wiki page, so the site looked okay to casual observers. As i was the only contributor to that repo, there was no need for me to follow the timeline, or i might have noticed the problem sooner in the form of timeline entries. Again: not an objection, just a cautionary tale. I appreciate this, after all, bots are getting more clever by the day! I am just not sure what I could go with without asking too much. Rob -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUMrRWAAoJEJV7oeIt3hbR1PUIAK9fMwXZm/MJhZMsC4uQkRcp kjHz/kLMeOpWwII/G0rf/oFmc/6P4jILsxpvG+I562J+ERQtVq6BRVzPx3oEwMJ9 yXuR2d5iFF4L6p5CYABoxL5M37PMVJOYbhuXKMWH2PycnS1cUsz71eHIcGEnQK0E ceFknJuG2XohGLNC+QXC5qlgUqgJEzbCYDpSqs7zGcvfUH3nlyUwllLLgcmtziMD SBWEK55Pfd8sOzwrLdUBEtzPD/3B71/XX62QbdzzdTV/6mEpIhH/c+yL1oTz13VL icV5hT6XBnmlzLMnC1guL6xUqHKuswJQMxUBwZCzhe2NPYSyCj4lDF6/oTxXAZE= =E0hO -END PGP SIGNATURE- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Quiet mode for update and sync
On Sun, Oct 5, 2014 at 11:05 AM, David Mason dma...@ryerson.ca wrote: (I do updates via ssh) If you are only doing updates via ssh, why run a cron job every 5 minutes? You could make a wrapper script for Fossil that runs Fossil to perform the sync, then backgrounds itself so the ssh session can disconnect and update the published area and send the email. If you are concerned about multiple near simultaneous updates, then when the script backgrounds, it could create a sentinel file in a specific directory, wait 5 mins then check for other sentinels. If there are, it removes the sentinel file and quits. If not, it updates the published area, sends the email then removes the sentinel file and quits. This isn't perfect, but it reduces your processing to only when repo content is needed. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] minor bug on export to git
When exporting to git, the check-in comments that are exported are the original comments. If you had subsequently edited the comments, then those edits are not retained during the export. Eric ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] minor bug on export to git
On Mon, Oct 6, 2014 at 1:14 PM, Eric Rubin-Smith eas@gmail.com wrote: When exporting to git, the check-in comments that are exported are the original comments. If you had subsequently edited the comments, then those edits are not retained during the export. Please try again with trunk. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Captcha and blind and visually impaired users
On Sun, Oct 5, 2014 at 1:34 PM, Rob robjo...@gmail.com wrote: Legend has it that on 05/10/2014 18:55, the fair wind whisper'd the words of Stephan Beal: i.e. what i'm afraid of is that once you start hosting a repo with such an option for the registration page, some bot is going to come along, register himself, and start flooding your tickets and wiki pages with... whatever it is that bots fill tickets and pages with. I think moderation can be helpful in this case, but it is a fairly thin line. If registering is too easy (i.e. it has no captcha or has something that can be defeated easily), bots might end up spamming the repository as you said. If the registration is too hard (e.g. takes too much time or is unsolvable), users are not going to register to report bugs, contribute to the wiki, etc. I can disable the self-register option, but in most cases, users would rather self-register than contact me for a registration request. An audio CAPTCHA is possible, but you would need help from a webserver to do this. Off hand, I can think of 2 options. 1. Have the webserver run Fossil as a CGI or SCGI, letting the webserver handle user management. This is the easiest. 2. Enhance Fossil to provide an encrypted copy of the secret string for use by the CGI/whatever that handles the audio CAPTCHA. (I can help with the encryption part.) And to have an alternate Javascript in the registration page that uses the CAPTCHA handling CGI/whatever instead of the auto-CAPTCHA. While the easiest way to handle a CAPTCHA would be to subscribe to one of the existing CAPTCHA services, you could do it by yourself. Maybe there are open source tools for implementing CAPTCHAs, but I don't know. If you decide to do it yourself, your CGI/whatever will need to generate some text, convert it to speech, send an audio file to the browser, then accept and verify the response. Your response handler will likely need to be tolerant of spelling variations. For the audio part, in the past (about 6 years ago) I have used eSpeak and Festival (both open source) for text-to-speech. As I recall, neither was hard to use. To avoid bots clever enough to have speech-to-text handling, I would suggest the generated audio describe something, including random details, then ask the user about 2 or 3 of the random details. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Is it possible to add empty folders to the repo?
(BETTER YET: Is it possible to REMOVE empty folders?) For me, there is an even more ‘annoying’ problem with the way empty directories are handled, but I think it is the opposite use case. For example: You have version X that has subdirectories a, b, and c. And, another version Y that has only a and b (c is missing, either because c isn’t yet created, or because c was removed, depending on whether version X comes before or after version Y). In either case, if you update from version X to version Y (using FOSSIL UPDATE command), the c directory is emptied but not completely removed even though it’s not part of the currently loaded version. This is quite a bit annoying, specially when you scale this problem to many such empty subdirectories.___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Tip: abusing autosync to abort a commit
Hi, all, (This just happened...) The autosync option provides (incidentally, not specifically by design) a feature one doesn't have if it is turned off: the ability to abort a commit within a small (and unknown/varying) time frame. For example: the intention here was to commit a single file, but 3 are actually modified: [stephan@host:~/cvs/fossil/cwal/s2]$ f com -m 'Minor build tweak.' Autosync: http://step...@fossil.wanderinghorse.net/repos/cwal/index.cgi ^C autosync gave me the time frame my brain needed to realize the mistake, giving me the opportunity to tap Ctrl-C. :) -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Tip: abusing autosync to abort a commit
On Oct 6, 2014 12:26 PM, Stephan Beal sgb...@googlemail.com wrote: Hi, all, (This just happened...) The autosync option provides (incidentally, not specifically by design) a feature one doesn't have if it is turned off: the ability to abort a commit within a small (and unknown/varying) time frame. For example: the intention here was to commit a single file, but 3 are actually modified: [stephan@host:~/cvs/fossil/cwal/s2]$ f com -m 'Minor build tweak.' Autosync: http://step...@fossil.wanderinghorse.net/repos/cwal/index.cgi ^C autosync gave me the time frame my brain needed to realize the mistake, giving me the opportunity to tap Ctrl-C. I have that functionality without auto sync. I don't use the -m comment option so I get a text editor showing me what has changed before I type the message. If I decide I need to not commit, I don't enter a message and fossil warns me allowing me to abort the conmit! :) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Tip: abusing autosync to abort a commit
Bah! Commit not conmit. Stupid phone keyboard. On Oct 6, 2014 12:39 PM, Scott Robison sc...@casaderobison.com wrote: On Oct 6, 2014 12:26 PM, Stephan Beal sgb...@googlemail.com wrote: Hi, all, (This just happened...) The autosync option provides (incidentally, not specifically by design) a feature one doesn't have if it is turned off: the ability to abort a commit within a small (and unknown/varying) time frame. For example: the intention here was to commit a single file, but 3 are actually modified: [stephan@host:~/cvs/fossil/cwal/s2]$ f com -m 'Minor build tweak.' Autosync: http://step...@fossil.wanderinghorse.net/repos/cwal/index.cgi ^C autosync gave me the time frame my brain needed to realize the mistake, giving me the opportunity to tap Ctrl-C. I have that functionality without auto sync. I don't use the -m comment option so I get a text editor showing me what has changed before I type the message. If I decide I need to not commit, I don't enter a message and fossil warns me allowing me to abort the conmit! :) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Tip: abusing autosync to abort a commit
On Mon, Oct 6, 2014 at 8:39 PM, Scott Robison sc...@casaderobison.com wrote: I have that functionality without auto sync. I don't use the -m comment option so I get a text editor showing me what has changed before I type the message. If I decide I need to not commit, I don't enter a message and fossil warns me allowing me to abort the conmit! :) Well... yeah... that'd be the easy way ;). i always use -m, simply out of long-standing habit. Your argument is a good reason to start weaning myself off of that, though. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Tip: abusing autosync to abort a commit
I just wanted to give you a little grief based on past -m comments. :) On Oct 6, 2014 12:42 PM, Stephan Beal sgb...@googlemail.com wrote: On Mon, Oct 6, 2014 at 8:39 PM, Scott Robison sc...@casaderobison.com wrote: I have that functionality without auto sync. I don't use the -m comment option so I get a text editor showing me what has changed before I type the message. If I decide I need to not commit, I don't enter a message and fossil warns me allowing me to abort the conmit! :) Well... yeah... that'd be the easy way ;). i always use -m, simply out of long-standing habit. Your argument is a good reason to start weaning myself off of that, though. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Tip: abusing autosync to abort a commit
On Mon, Oct 6, 2014 at 2:41 PM, Stephan Beal sgb...@googlemail.com wrote: On Mon, Oct 6, 2014 at 8:39 PM, Scott Robison sc...@casaderobison.com wrote: I have that functionality without auto sync. I don't use the -m comment option so I get a text editor showing me what has changed before I type the message. If I decide I need to not commit, I don't enter a message and fossil warns me allowing me to abort the conmit! :) Well... yeah... that'd be the easy way ;). i always use -m, simply out of long-standing habit. Your argument is a good reason to start weaning myself off of that, though. Hmm. I seem to recall you extolling the virtues of command line editing. :) I confess I didn't think if this an a reason to use an actual editor. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Tip: abusing autosync to abort a commit
On Mon, Oct 6, 2014 at 9:05 PM, Ron W ronw.m...@gmail.com wrote: Hmm. I seem to recall you extolling the virtues of command line editing. :) Touché! (That's a word we don't get to use nearly enough in everyday speech!) I confess I didn't think if this an a reason to use an actual editor. Agreed! -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Tip: abusing autosync to abort a commit
On Mon, Oct 6, 2014 at 9:00 PM, Scott Robison sc...@casaderobison.com wrote: I just wanted to give you a little grief based on past -m comments. :) LOL! i expected you might be, but wasn't sure if you had arrived on the list the last time that topic came up. But seriously, though, your argument is a good reason not to use -m and rely on $EDITOR instead. i think my problem is that i regularly use 2 (sometimes 3) SCMs, namely fossil, svn, and (sometimes) git, often over a remote connection on systems with no emacs installed (and emacs takes too long to start for a short commit message). So -m just kind of became baked in to my fingers at some point :/. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Tip: abusing autosync to abort a commit
On Mon, Oct 6, 2014 at 3:05 PM, Stephan Beal sgb...@googlemail.com wrote: But seriously, though, your argument is a good reason not to use -m and rely on $EDITOR instead. i think my problem is that i regularly use 2 (sometimes 3) SCMs, namely fossil, svn, and (sometimes) git, often over a remote connection on systems with no emacs installed (and emacs takes too long to start for a short commit message). So -m just kind of became baked in to my fingers at some point :/. I don't know about emacs, but there was (maybe still is) a minimal version of vi I used to use for situations like this. Maybe there is a minimal version of emacs? (I suppose, technically, an old enough version could be considered minimal, but I mean an actively maintained project whose goal was (is?) to provide a lightweight version with a small, but complaint, subset of the features.) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Captcha and blind and visually impaired users
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Legend has it that on 06/10/2014 19:42, the fair wind whisper'd the words of Ron W: An audio CAPTCHA is possible, but you would need help from a webserver Do youthink it would be possible to implement a very simple textual captcha that randomizes a few numbers and a few operations and asks for the result? I think that should be fairly secure, especially if we output numbers as letters (one, two, etc). This would remain faithful to Fossil's single-file nature and might be even integrated into the official Fossil release, as a toggleable option. Rob -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUMutyAAoJEJV7oeIt3hbRj7cH+gIYg2YwBUMZF0PalYW7n+bC W2ZBmPoRJb2Fljh3s+F/FTSa6TkMd6Ag7EZrO0vEZRopR4/b5rG2OPuGjDT8ij0b q1vOblT5bz6wnQAkdjwshTAv7kFWyt8/ybEom0ePCrxI/37Fe6/B0CGFTtOfob/B TtMqOJQ4SNu36gOhJnW7jQ5CrdGZQiKKwMWal9smIZcZ66lBOXWMmv1nB5Xbx9ID LpydKyX/NeTEs2BJCM8AiJIDyaaJiznGjwaKDAaortJgD0RvdMGx9iYkLmmX+YPS V0jJq/SRAMEeItpdIRjeBojHmkjlLgqWsT7PKkJxCqSFssl+8G0wYAKconsgkMg= =A4B4 -END PGP SIGNATURE- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Tip: abusing autosync to abort a commit
Thus said Stephan Beal on Mon, 06 Oct 2014 20:25:55 +0200: The autosync option provides (incidentally, not specifically by design) a feature one doesn't have if it is turned off: the ability to abort a commit within a small (and unknown/varying) time frame. joke Perhaps there should be a known and variable configuration setting that gives you that brief amount of time on purpose? ;-) fossil commit-wait-interval 5 Will wait for 5 seconds before actually attempting to commit anything. /joke Andy -- TAI64 timestamp: 40005432eedb ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Tip: abusing autosync to abort a commit
On Mon, Oct 6, 2014 at 1:34 PM, Andy Bradford amb-fos...@bradfords.org wrote: Thus said Stephan Beal on Mon, 06 Oct 2014 20:25:55 +0200: The autosync option provides (incidentally, not specifically by design) a feature one doesn't have if it is turned off: the ability to abort a commit within a small (and unknown/varying) time frame. joke Perhaps there should be a known and variable configuration setting that gives you that brief amount of time on purpose? ;-) fossil commit-wait-interval 5 Will wait for 5 seconds before actually attempting to commit anything. /joke My first year of college I took a fortran (I mean FORTRAN) class. Our lab was hosted on big heavy terminals connected to a mainframe. In any case, the newbie friendly system had a triple prompt any time you tried to delete a file from your workspace: 1. Delete filename (y/n)? 2. Are you sure you want to delete filename (y/n)? 3. Last chance! Are you really sure you want to delete filename (y/n)? Naturally, muscle memory kicks in before long and you get used to hitting D Y Y Y in quick succession to delete a file. Which I did once. I blamed myself for not thinking it through. And later as a TA for the class I dealt with a few students who had the same problem. Students were more apt to blame me (even though there was nothing I could have done about it). :) Anyway... yeah. Not all safety systems are very safe. :) -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Cloning repo
Thus said Stephan Beal on Mon, 06 Oct 2014 17:23:22 +0200: http://www.fossil-scm.org/index.html/info/165cc5c093e6ee36a78de5e01f7049235dbc1b1c?ln=1856-1867 Could i convince you to give that look? Yes, I'll look at it again later. I looked at it briefly before just long enough to remind myself of where it was relevant and didn't see any obvious problems. I couldn't seem to produce any problems either, but I really only tried it with sync and not clone operations. I believe the only time it will be relevant for a clone operation is the very first sync operation. Andy -- TAI64 timestamp: 40005432f0e7 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Tip: abusing autosync to abort a commit
On 06/10/14 19:41, Scott Robison wrote: Bah! Commit not conmit. Stupid phone keyboard. On Oct 6, 2014 12:39 PM, Scott Robison sc...@casaderobison.com mailto:sc...@casaderobison.com wrote: On Oct 6, 2014 12:26 PM, Stephan Beal sgb...@googlemail.com mailto:sgb...@googlemail.com wrote: Hi, all, (This just happened...) The autosync option provides (incidentally, not specifically by design) a feature one doesn't have if it is turned off: the ability to abort a commit within a small (and unknown/varying) time frame. For example: the intention here was to commit a single file, but 3 are actually modified: [stephan@host:~/cvs/fossil/cwal/s2]$ f com -m 'Minor build tweak.' Autosync: http://step...@fossil.wanderinghorse.net/repos/cwal/index.cgi ^C autosync gave me the time frame my brain needed to realize the mistake, giving me the opportunity to tap Ctrl-C. I have that functionality without auto sync. I don't use the -m comment option so I get a text editor showing me what has changed before I type the message. If I decide I need to not commit, I don't enter a message and fossil warns me allowing me to abort the conmit! :) Or alternatively use a GUI. Here's mine: http://wiki.tcl.tk/39369 Once you press the commit button it gives you a summary, e.g. 3/3 modified files are selected for checking in. At which point you might notice and press the cancel button. Hopefully soon I'll have the code available at www.p-code.org, I'm just going through the process of finding a suitable host. My first stop is TuxFamily, but we'll see ... Regards ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Tip: abusing autosync to abort a commit
On 6 October 2014 15:05, Stephan Beal sgb...@googlemail.com wrote: good reason not to use -m and rely on $EDITOR instead. i think my problem is that i regularly use 2 (sometimes 3) SCMs, namely fossil, svn, and (sometimes) git, often over a remote connection on systems with no emacs installed (and emacs takes too long to start for a short commit message). http://en.wikipedia.org/wiki/MicroEMACS or mg fossil set --global editor /usr/local/bin/mg and type emacs once per boot for your real editing environment (and you can even point $EDITOR to emacsclient since fossil has its own editor setting). Now if there was a setting for throw whatever I type after -m into an edit buffer anyway then you could continue to use -m for those other SCMs and fossil would protect you. ../Dave ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Tip: abusing autosync to abort a commit
The problem is access - i don't have root access on most systems, and many others don't have compilers, or have quota limitations, weird/old OS versions, etc. So -m, which works the same in all environments, has become what my fingers just do without having to be told. - stephan Sent from a mobile device, possibly from bed. Please excuse brevity and typos. On Oct 6, 2014 10:06 PM, David Mason dma...@ryerson.ca wrote: On 6 October 2014 15:05, Stephan Beal sgb...@googlemail.com wrote: good reason not to use -m and rely on $EDITOR instead. i think my problem is that i regularly use 2 (sometimes 3) SCMs, namely fossil, svn, and (sometimes) git, often over a remote connection on systems with no emacs installed (and emacs takes too long to start for a short commit message). http://en.wikipedia.org/wiki/MicroEMACS or mg fossil set --global editor /usr/local/bin/mg and type emacs once per boot for your real editing environment (and you can even point $EDITOR to emacsclient since fossil has its own editor setting). Now if there was a setting for throw whatever I type after -m into an edit buffer anyway then you could continue to use -m for those other SCMs and fossil would protect you. ../Dave ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Captcha and blind and visually impaired users
On Mon, Oct 6, 2014 at 3:20 PM, Rob robjo...@gmail.com wrote: Do youthink it would be possible to implement a very simple textual captcha that randomizes a few numbers and a few operations and asks for the result? I think that should be fairly secure, especially if we output numbers as letters (one, two, etc). This would remain faithful to Fossil's single-file nature and might be even integrated into the official Fossil release, as a toggleable option. It is doable, but a bot would still be able to read and interpret it. Assuming any of the existing CAPTCHA services support a mode of operation where Fossil could generate an encrypted URL to include in the registration page (as opposed to Fossil sending a request to the service), then I would suggest that the best way for Fossil to support CAPTCHAs for the visually impaired would be to provide the needed TH1 primitives to enable a TH1 script to generate the required HTML and encrypted secret string to include in the registration page. FYI, even if a text-based version of what I described for an audio CAPTCHA were used, I'm pretty sure there are bots that could pass the test. (When presented as text, my test essentially amounts to a reading comprehension test. Also, several top tier universities have open source natural language processing projects that are, supposedly, very good.) There are word puzzles that, so far, only humans can solve, but (a) these may be too hard for a CAPTCHA and (b) they almost always have more than 1 correct answer. (But I'm far from an expert in word puzzles, so I would not know what to suggest as puzzles.) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Captcha and blind and visually impaired users
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Legend has it that on 06/10/2014 22:35, the fair wind whisper'd the words of Ron W: It is doable, but a bot would still be able to read and interpret it. Theoretically speaking, making an automatic captcha solver for Fossil's current ascii art captcha is not really hard to do. The question is how far is anyone willing to go to defeat any captcha? I have been using a very simple solution to keep out spammers for a few years now, alongside the math puzzles. My registration form has a checkbox, that simply says I am a spammer. Most bots select and check form controls, just in case the form needs it to be checked when validating. Of course, if this checkbox is checked, the site is not going to accept the form submission. These are very easy to defeat, but the site has to be specifically targeted. If that happens, it is trivial to log in with a manually created account and create havoc. Assuming any of the existing CAPTCHA services support a mode of operation where Fossil could generate an encrypted URL to include in the registration page (as opposed to Fossil sending a request to the service), then I would suggest that the best way for Fossil to support CAPTCHAs for the visually impaired would be to provide the needed TH1 primitives to enable a TH1 script to generate the required HTML and encrypted secret string to include in the registration page. While they can be great (see Akismet), I'd rather not use captcha services outside Fossil. Rob -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUMw7uAAoJEJV7oeIt3hbRHBIH/ApOj4gcl8sWJu3jxe/U24jt QFpAVlAqiC8fSifzHDCEKiA8JIokV+mtGwm6uksj+NGv4EMCyUX1CwyzCni1x2LZ 3d3rOVT2+72TRnNAKAccLDmBBy3tTwIvG6Ebk6R3p0jO1pvSdgyO4PIu/rtFY4OA o7n0yDOysQiK/ahkUZXlY4yqh2ak99pZ9GJUYb5NN1aRTf3p+LacuRD0ryIP0pjQ Z7Rfth2oiwTYgriCThF+nJ8By+OarJ3n7BZB9sscICLgoZULhnk2FyMTg14RNxYV U2s/FAwZeGhOp4qB5ZJyGwRvwGz4hwTfpUUcn/zcDYrEUgFp0FKqQBHLUtBG8qc= =0w+0 -END PGP SIGNATURE- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Cloning repo
Stephan, Andy, Thanks for the quick action re my issue. I'll test it as soon as I have a little more time (end of this week?). Best, Jacek 2014-10-06 16:23 GMT+01:00 Stephan Beal sgb...@googlemail.com: On Mon, Oct 6, 2014 at 6:24 AM, Andy Bradford amb-fos...@bradfords.org wrote: After looking at it, I don't think this introduces any unwanted side effects. :-D autosync-tries dictates how many times ``autosync'' should ...autosync-tries would be honored and one would have to enter the password for a maximum of 2 * autosync-tries. That's what it looked like to me. Potentially annoying but harmless (and abortable with a Ctrl-C). Maybe if we could distinguish between password failure and other Seems to me to be rare corner case which isn't necessary. Maybe in certain setups/uses, but i can't say i'd ever conceived of this problem until Jacek (the OP) posted it. For the archives, here is what happens when I have autosync-tries set to 2 and a password failure: ... Autosync failed. continue in spite of sync failure (y/N)? n $ Seems to behave as I would expect. Any other opinions? Agreed. No less surprising result for that case comes to mind. But now that you mention autosync retry count... i'm not 100% sure i put that ++nErrs in the right place: http://www.fossil-scm.org/index.html/info/165cc5c093e6ee36a78de5e01f7049235dbc1b1c?ln=1856-1867 Could i convince you to give that look? -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
