Hi Martyn,
Martyn Jago martyn.j...@btinternet.com writes:
There are literally hundreds of uses of #+srcname and #+source within
Worg - should I be updating these to #+name ? In other words, does Worg
reflect the last official release (the Emacs release), or the bleeding
edge (I tend to
On Wed, Nov 23 2011, Sebastien Vauban wrote:
Hi Nick,
Nick Dokos wrote:
Martyn Jago martyn.j...@btinternet.com wrote:
There are literally hundreds of uses of #+srcname and #+source within
Worg - should I be updating these to #+name ? In other words, does Worg
reflect the last official
Hi Nick,
Nick Dokos wrote:
Martyn Jago martyn.j...@btinternet.com wrote:
There are literally hundreds of uses of #+srcname and #+source within
Worg - should I be updating these to #+name ? In other words, does Worg
reflect the last official release (the Emacs release), or the bleeding
edge
Sebastien Vauban wxhgmqzgw...@spammotel.com wrote:
Is there any way to find out what the org version is at the worg site?
BTW, sorry, yes, the answer is yes: see section What software is available on
Worg for Babel code execution? on http://orgmode.org/worg/worg-setup.html.
But one can
Hi Nick,
Nick Dokos wrote:
Sebastien Vauban wxhgmqzgw...@spammotel.com wrote:
Is there any way to find out what the org version is at the worg site?
BTW, sorry, yes, the answer is yes: see section What software is available
on
Worg for Babel code execution? on
Hi
There are literally hundreds of uses of #+srcname and #+source within
Worg - should I be updating these to #+name ? In other words, does Worg
reflect the last official release (the Emacs release), or the bleeding
edge (I tend to assume the latter because of the Org community spirit of
Worg),
Martyn Jago martyn.j...@btinternet.com wrote:
There are literally hundreds of uses of #+srcname and #+source within
Worg - should I be updating these to #+name ? In other words, does Worg
reflect the last official release (the Emacs release), or the bleeding
edge (I tend to assume the latter