On 5/18/2015 7:48 AM, Ramon Ribó wrote:
I tried andygoth-brackets-outside-links. I like it better the old
way, with the brackets as part of the hyperlinks
With current fossil, it is not possible to cut and paste from browser
to command line a version number. The brackets get attached to the
copied text and it is necessary to manually edit the command line to
remove them. I think that the alternate method avoids this problem.
Thinking outside the box for a moment, what problems arise if we permit
an SHA1 prefix in square brackets to mean the obvious thing when typed
at the command prompt?
I suppose one obvious issue is that [] are special to the shell in *nix
flavors, and so would need quoting. But on Windows, they aren't special, and
fossil info [abcd]
could be interpreted as the same as
fossil info abcd
by just dropping the brackets if they are present. I suppose that would
prevent naming a tag with surrounding square brackets, but is that
actually permitted now and if so, should it be?
If brackets were allowed and ignored at the command line, the copy paste
issue would be mitigated.
That said, I personally don't mind pushing the brackets outside of the
link, but don't feel strongly enough either way to take a position.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
_______________________________________________
fossil-dev mailing list
fossil-dev@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
