From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Updating Worg re standard source block syntax
Date: Wed, 23 Nov 2011 11:30:33 +0100 [thread overview]
Message-ID: <80k46ri112.fsf@somewhere.org> (raw)
In-Reply-To: 14015.1322002898@alphaville.americas.hpqcorp.net
Hi Nick,
Nick Dokos wrote:
> Martyn Jago <martyn.jago-FhtRXb7CoQBt1OO0OYaSVA@public.gmane.org> 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 because of the Org community spirit of
>> Worg), but I fail to find any specific notice regarding this.
>>
>> Advice would be appreciated since I've found myself appreciating, and
>> adding to Worg more and more - and it seems to me it is a real quality of
>> Org that Worg can exist in the first place.
>>
>
> Is there any way to find out what the org version is at the worg site?
> This is something that I've wondered about in the past, but I keep
> forgetting to ask the question. E.g. it would be good to know the
> version, so when I make a change to worg content and test the change by
> publishing the site locally, I can use the exact version that is going
> to be used on the real site. Right now, I test with whatever version is
> running on my machine, which can lead to false conclusions (both positive
> and negative).
IIUC, the answer is no. But the best place for such information should be in
the output log of the publish process, that is at
http://orgmode.org/worg/publishing.txt
Adding
(message "Org-mode %s on Emacs %s." org-version emacs-version)
-- or something alike -- in http://orgmode.org/worg/sources/emacs.el should do
it.
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 wonder if it's up-to-date. That's why adding it as proposed should
be done anyway.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2011-11-23 10:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 21:43 Updating Worg re standard source block syntax Martyn Jago
2011-11-22 22:18 ` Nick Dokos
2011-11-22 23:01 ` Nick Dokos
2011-11-23 10:30 ` Sebastien Vauban [this message]
2011-11-23 15:12 ` Nick Dokos
2011-11-23 15:31 ` Sebastien Vauban
2011-11-30 22:06 ` Jason Dunsmore
2011-12-15 13:55 ` Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=80k46ri112.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).