On May 11, 2016, at 3:52 PM, Marko Käning <sec001+fos...@posteo.net> wrote: > > Referring to tickets on a wiki page like this: [968eb6376d] doesn't work, > where one would have to use [968eb6376d](tktview?name=968eb6376d). > > Is this intended, or am I missing something?
Yes, it’s a known limitation. This missing feature came up in a thread a month or two ago, but there were objections that allowing [12345abc] to automatically link to a ticket could be ambiguous: 1. The case of [123] possibly matching two or more tickets (or other artifact types!) is easy to deal with in an ad hoc basis, not involving Fossil at all: add more digits to the link until the meaning of the reference is no longer ambiguous. 2. A more serious issue is that the syntax is somewhat ambiguous within the syntax of Markdown itself. It is legal to say [foo] [1], with the expectation that a link reference will follow later in the document: [1]: http://example.com Therefore, if the Fossil Markdown processor came across [123], it would have to have two cases in its path: internal Markdown link or checkin comment like link to an artifact ID. I think this objection is also fairly easily demolished: try to find an internal link reference first if the value in the brackets is a base-10 integer, then try to find a suitable artifact if that fails. And if the value in the brackets can only be a base-16 integer, skip straight to the artifact search. To expand on your request, I also think you should be able to say things like …bla bla bla but there is a [plan](1235abc) to fix that. in a wiki article that wants to refer to a ticket. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
