On 4/20/2014 11:29 AM, Joe Mistachkin wrote:
Unless I'm wrong, I seem to recall that there is a setting to make the
timeline permit wiki and/or HTML markup for check-in comments.
I pulled all my release code into the Fossil repository. Here's how it
looks:
https://chiselapp.com/user/andy/repository/wibble/timeline?n=200&y=ci
To be done:
- Create branches for contributed/forked code.
- Publish documentation and examples.
- Create tickets for outstanding bugs.
- Rearrange code now that it's feasible to have multiple files.
- Remove Wibble code and such from the Tcl wiki and redirect to chiselapp.
It bothers me that I will forevermore have to be careful about putting
<, >, and & in my check-in comments. I've already had to make several
edits to fix this.
I would prefer a more flexible wiki markup. In the future Fossil may
grow an admin-selectable secondary wiki markup language that doesn't
resort to HTML notation for things like nested lists. But when this is
done, it would also be useful to get a conversion utility that parses
existing comments and wiki pages and converts to the more advanced
style. The purpose, the very definition, of a lightweight markup
language such as wiki is to be easily readable in plain text form.
Tossing <ul> and <li> and </li> and <a href> and such all over the place
is contrary to that goal.
Are there any standardized wiki markup languages worth targeting, or
does every wiki engine roll its own?
--
Andy Goth | <andrew.m.goth/at/gmail/dot/com>
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
