> On Thu, Aug 2, 2012 at 7:01 PM, <v...@lavabit.com> wrote: > >> succeed adding it to a fossil repo so I can use its functionality in >> wiki >> pages (like I managed to do with a custom source code highlighter long >> ago). >> > > The "custom pages/commands" feature, currently very early in development, > should allow users to plug in this type of functionality without code > changes. i will be sure to keep this particular use case in mind while > developing that.
By integrating a javascript library I just mean adding the javascript code to the fossil repo header and having a way of just making it work when the fossil page is loaded in the browser. Of course, without any code changes to fossil (I wouldn't be able to do that anyway). > It "might be interesting" for us to simply tweak the current diff command > to be able to htmlify its output in CLI mode. Then you could at least > script-generate the diffs for inclusion in your pages. Or even add a new > diff alternative which reads two arbitrary files (local files, not repo > artifacts) and outputs a diff (optionally htmlified). That might also > allow > one to more diff a local file which was renamed against its older name in > the repo, e.g. fossil xdiff fileInRepo someLocalFile. Internally, the diff > routine doesn't care where its input comes from. > > Would such features be useful for your case? (i'm not promising anything > in > the near future, but i like having a few things on the todo list.) > I did some more investigation and it seems I can htmlify diffs with vim. The :TOhtml command doesn't seem to work for me when vim is in diff mode, but the vim plugin formatvim (http://www.vim.org/scripts/script.php?script_id=3113) seems to do the job nice. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
