Arnaud Bailly <[EMAIL PROTECTED]> writes: > Hello, > A while ago I posted an announcement about the availability of a Java > parser for the muse format. I just released a new version tagged > 1.0-rc3 that, among bug fixes and minor issues add a "literate > programming" feature: One can embed source code into its muse pages > and a backend extracts it to files that can later be > processed/intepreted/compiled... The whole thing is available at > > http://www.oqube.com/projects/muse-java > > I currently use this feature in the context of the maven build system, > thus allowing me to write my projects documentation under emacs-muse > and publish it with maven to XHTML. Maven give me the opportunity to > compile automatically generated source files and even execute embedded > test cases. > > My question is: How can I add this feature to emacs-muse so that my > <source> tag get recognized under emacs ?
So it puts <perl>, <python>, etc. regions into separate files and then compiles/interprets them? How does it decide what to name the files? How does it decide what interpreter/compiler to install? -- Michael Olson -- FSF Associate Member #652 -- http://www.mwolson.org/ Interests: Emacs Lisp, text markup, protocols -- Jabber: mwolson_at_hcoop.net /` |\ | | | IRC: freenode.net/mwolson: #emacs, #hcoop, #muse, #PurdueLUG |_] | \| |_| Projects: Emacs, Muse, ERC, EMMS, Planner, ErBot, DVC
pgpqna2TD8i4S.pgp
Description: PGP signature
_______________________________________________ Muse-el-discuss mailing list [email protected] https://mail.gna.org/listinfo/muse-el-discuss
