This is great news! Does this mean commit comments will respect embedded [CR+LF] characters in the Timeline view?
Happy Thanksgiving all you American users :) On Thu, Nov 22, 2012 at 11:23 AM, Ramon Ribó <ram...@compassis.com> wrote: > > Comments and tickets are already text only. The point here is that in some > very specific contexts (timeline) and under demand (there is a setting), > they can be displayed as being wiki text. As this is optional, I do not see > the point to make it disappear. > > However, with some very simple modifications, the possibility of displaying > bad a user comment would be greatly reduced. > > In our daily practice, we use mainly 3 wiki capabilities for the comments > and tickets: > > > * <b>bold</b> [link] > > In my opinion the best option would be to perform the following actions: > > > 1) Improve slightly the wiki syntax: > > *[space] == [space]*[space] == [space][space]*[space][space] > > **bold** == <b>bold<b> (note: other syntaxes are possible: ''bold'' > *bold*, just choose one) > > > 2) Take some care when displaying wiki syntax: > > a) Any use of [] that does not point a real link, consider it as normal > text > > b) Any use of <> that is not a recognized html tag consider it as > normal text > > > With a wise use of 2a) and 2b) there should be nearly no cases where a text > only comment is displayed bad. > > Regards, > > > Ramon Ribó > > > > 2012/11/22 Jan Nijtmans <jan.nijtm...@gmail.com> >> >> 2012/11/22 Michal Suchanek <hramr...@gmail.com>: >> > On 22 November 2012 14:35, Jan Nijtmans <jan.nijtm...@gmail.com> wrote: >> >> I think I would fix that in the comment preprocessor. >> > The major disadvantage is, of course, that this ugly mess will be >> > likely visible in the command line view of the commits and that it >> > does not allow changing the commit message format. And this whole >> > thing is probably about allowing multiple commit formats to exist >> > cleanly in one repo. >> >> The timeline view already has code to display the comment text >> without format, that could be used for eventual command-line >> output as well. It's only comment anyway. >> >> Another functionality of fossil is that the commit-message is >> saved in case the commit fails, as initial value for the next >> try. This message will have to be saved before the tag >> replacements. Sometimes the initial commit-message comes >> from another commit. The formatting would have to be >> removed then. Hm.... >> >> I'm not sure yet that this is the best solution, but thats >> - eventually - for Richard to decide. Now it's still >> brainstorming time. >> >> Regards, >> Jan Nijtmans >> _______________________________________________ >> 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 mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
