It is an unexpected change from prior behavior. I am used to writing a wiki page, putting things in [brackets] where I expect to make a page, and then click on the links to create the page. Much nicer than being forced to go to the wiki creation page and typing in the name.
Perhaps there's a middle ground solution? On 11/20/2012 02:28 PM, Richard Hipp wrote: > > > On Tue, Nov 20, 2012 at 4:32 AM, Lluís Batlle i Rossell > <[email protected] <mailto:[email protected]>> wrote: > > On Tue, Nov 20, 2012 at 06:20:02AM +0000, K wrote: > > > > This is as a result of a featured added on my behalf, I'm afraid. > > > > There should now be (I haven't found occasion to update my > Fossil to 1.24 > > given I'd have to repatch the wiki page name length requirement) > an option > > somewhere allowing the treatment of [xxx] as wiki mark up. > > Sorry, what is this new feature about, and its consequences? And > the motivation > of the change? > > I might have missed the rationale. > > > The idea is that when you have text like "[something]" in a check-in > comment or ticket, if "something" is not a real hyperlink target (if > it is not the name of a check-in or wiki page or ticket or a URL) then > do not try to convert it into a hyperlink. That way, code snippets > that contain [...] do not have to escape the [...]. > > And example. In http://www.fossil-scm.org/fossil/info/10aee063c4 on > the 2012-11-19 07:31:25 comment by anonymous, you can see an unescaped > "[]". This is rendered in red prior to the recent change - and (as of > this writing) is still shown in red on www.fossil-scm.org > <http://www.fossil-scm.org> since I have not recompiled the Fossil on > www.fossil-scm.org <http://www.fossil-scm.org> yet. But if you look > at the same ticket using the very latest Fossil, the Fossil that > includes the change, the [] is shown correctly. > > Lots and lots of people have been requesting this change, since it > makes it so much easier to type check-in comments and tickets. Most > users, I am told, expect that check-in comments and tickets will be > plain text, without markup. Decorating real hyperlinks is OK, but one > should not change the text in any way, I am told. This latest change > is a move in that direction. > > Please tell me why you think this is not a good idea? If necessary, > it can be made optional. But I couldn't think of a reason to display > broken links in red rather than just not transforming them at all. > > > -- > D. Richard Hipp > [email protected] <mailto:[email protected]> > > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
