On Thu, Aug 2, 2018 at 12:59 PM Artur Shepilko <nomadb...@gmail.com> wrote:
> The rationale is to leverage the usual IDE conveninces such as code > browsing, auto-complete, visual debugger etc. Also, having a Fossil > source control plugin helps navigating the changes. > One forewarning about code browsing: the build process filters the files under src/, copying them to bld/, which means that if you accidentally browse (via "symbol-following" features) into bld/*.c and start editing, any changes will be lost the next time you build. Been there, done that. Also, many C files under src/ use custom markup (lines starting with @) which will confuse most C editors (any which do syntax highlighting). That's only "cosmetic confusion", though - it doesn't break anything. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
