Re: [fossil-users] Automatic password remembrance in fossil clone
On Thursday, August 28, 2014 6:41 AM, Andy Bradford wrote: Thus said Andy Gibbs on Wed, 27 Aug 2014 18:58:21 +0200: Is there a rationale behind this? Could there be a flag (e.g. -q / --quiet would work!) that can do an automatic yes at this point? I'm not sure about the rationale except perhaps it could be ambiguous. There are potentially other prompts that could be issued during cloning. So simply echoing y into the fossil clone command could be ambiguous. Yes, this is the worst-case high-maintenance option, but surprisingly common! Would the -q / --quiet apply an implied y to the username/password prompt only or would others be impacted? Ordinarily a quiet option would take the default value for any prompts. The prompts have default values already (in this case, simply hitting return means yes). This would actually be quite a neat solution since it seems fossil factors out prompts into their own functions, so on entering the function it can determine whether the -q option has been given and return the default value for that prompt. I would assume, that would mean a blank password where the password is prompted, for example. I would advocate the quiet option being global for all fossil commands. Maybe a --keep-password option would be less ambiguous? Alternatively, if you're scripting the clone with a username/password, have you considered scripting the syncs with the same username/password? I did, but there are a number of different scripts. From a script durability point of view, it would be good, since fossil *can* remember passwords, for it to do so during clone. Cheers, Andy (another one) Andy -- TAI64 timestamp: 400053feb33a ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Automatic password remembrance in fossil clone
Hi, It seems (at least in v1.29) that it is not possible to do a fossil clone with a username and password in the url and automatically remember the password via a command line switch or other approach. What is really interesting is that if you pipe y into the fossil clone command, then fossil doesn't even ask to remember the password. It seems that the user must be prompted, which is a problem when scripting! I've tracked it down in the source code in url.c, function url_parse_local(...) where it explicitly checks isatty(fileno(stdin)) and otherwise doesn't apply the URL_REMEMBER_PW flag at all. Is there a rationale behind this? Could there be a flag (e.g. -q / --quiet would work!) that can do an automatic yes at this point? Thanks!!! Andy ___ 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] Automatic password remembrance in fossil clone
On Wed, Aug 27, 2014 at 6:58 PM, Andy Gibbs andyg1...@hotmail.co.uk wrote: Is there a rationale behind this? Could there be a flag (e.g. -q / --quiet would work!) that can do an automatic yes at this point? FWIW: can't answer those questions definitively, other than an abstract seems sane to the -q flag, but can confirm the behaviour you're reporting. -- - 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] Automatic password remembrance in fossil clone
Thus said Andy Gibbs on Wed, 27 Aug 2014 18:58:21 +0200: Is there a rationale behind this? Could there be a flag (e.g. -q / --quiet would work!) that can do an automatic yes at this point? I'm not sure about the rationale except perhaps it could be ambiguous. There are potentially other prompts that could be issued during cloning. So simply echoing y into the fossil clone command could be ambiguous. Would the -q / --quiet apply an implied y to the username/password prompt only or would others be impacted? Maybe a --keep-password option would be less ambiguous? Alternatively, if you're scripting the clone with a username/password, have you considered scripting the syncs with the same username/password? Andy -- TAI64 timestamp: 400053feb33a ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
