On 3 August 2012 16:43, Stephan Beal <[email protected]> wrote: > On Fri, Aug 3, 2012 at 4:30 PM, Michal Suchanek <[email protected]> wrote: >> >> I don't think that doing this is desirable. fossil status should be >> fossil status. > > > And i agree entirely, i just posted the idea as a possible extension of the > custom commands (since this is an evolutionary process, and custom commands > will enable new directions for growth).
I guess renaming commands (or replacing or aliasing, ..) could be a local configuration, similar to user accounts used for the web UI, CR/LF conversion, commiter email, and whatnot. Then you can have a custom command synced from upstream and locally alias it to replace one of the standard commands - or not. >> >> Still if you are editing and >> testing the pages in the browser it might be good idea to make >> whatever you save a 'checkout' which is only synced when you 'commit' >> it. Otherwise you are going to make tons of small meaningless commits >> as you edit small details of templates and stylesheets. > > > This could be done using something like the wiki's preview feature, where > the client submits wiki content and the server renders it without saving it. This is rather difficult currently. You have to use force-refresh for CSS changes to show in the browser. Could be easily fixed with referencing style-draft-<date>.css or style-<version>.css rather than style.css. Or with a proper date and cache control in the header I guess. Thanks Michal _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
