On Sat, Jul 7, 2018 at 2:12 PM Martin Gagnon <eme...@gmail.com> 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
