Re: [fossil-users] Can't believe --branchcolor would be platform-specific
On Sat, Jul 07, 2018 at 02:39:52PM +0200, Francois Vogel wrote: > Many thanks for your answers. I'm always impressed how members of this > list are helpful and reply quickly. Bienvenue -- Martin G. ___ 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] Can't believe --branchcolor would be platform-specific
Many thanks for your answers. I'm always impressed how members of this list are helpful and reply quickly. Regards, Francois ___ 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] Can't believe --branchcolor would be platform-specific
On Sat, Jul 7, 2018 at 2:12 PM Martin Gagnon wrote: > My guess is that on a bash shell, # is the symbol for comments. Try to put > it in double quotes; >e.g.:—branchcolor "#f0a0a0" > That is definitely what's happening, and it's not bash-specific: every[^1] Unix-style shell known to man treats an unescaped # as the start of a comment. An alternate approach, aside from quotes is: --branchcolor \#f0a0a0 [1] = obviously, since i say "every" in public, someone will now point out an exception to that rule. That said, i'm not aware of any exceptions. -- - stephan beal http://wanderinghorse.net/home/stephan/ "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] Can't believe --branchcolor would be platform-specific
My guess is that on a bash shell, # is the symbol for comments. Try to put it in double quotes; e.g.:—branchcolor "#f0a0a0" Regards, (Sorry for top posting and brevity, I’m on mobile) — Martin G. Le sam. 7 juill. 2018 à 07:30, Francois Vogel a écrit : > Hi all, > > I'm experiencing the following error on macOS and Linux: > > $ f commit -m "Fix bug" --branch mybranch --branchcolor #f0a0a0 > unrecognized command-line option, or missing argument: --branchcolor > $ fossil version > This is fossil version 2.6 [9718f3b078] 2018-05-04 12:56:42 UTC > $ f commit -m "Fix bug" --branch mybranch > New_Version: > > The same command with --branchcolor, succeeds on Windows (but here I'm > using fossil-2.1). > > Any thoughts on this perhaps? Couldn't find the light reading the > documentation, I can't see why the --branchcolor option would be > platform-specific. Or is it that this option got removed since 2.1 > ?'fossil help commit' still documents it however. > > Thanks! > Francois > > ___ > 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
[fossil-users] Can't believe --branchcolor would be platform-specific
Hi all, I'm experiencing the following error on macOS and Linux: $ f commit -m "Fix bug" --branch mybranch --branchcolor #f0a0a0 unrecognized command-line option, or missing argument: --branchcolor $ fossil version This is fossil version 2.6 [9718f3b078] 2018-05-04 12:56:42 UTC $ f commit -m "Fix bug" --branch mybranch New_Version: The same command with --branchcolor, succeeds on Windows (but here I'm using fossil-2.1). Any thoughts on this perhaps? Couldn't find the light reading the documentation, I can't see why the --branchcolor option would be platform-specific. Or is it that this option got removed since 2.1 ?'fossil help commit' still documents it however. Thanks! Francois ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
