From: Jason Dunsmore <jasondunsmore@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Updating Worg re standard source block syntax
Date: Wed, 30 Nov 2011 16:06:05 -0600 [thread overview]
Message-ID: <87y5uxb702.fsf@riotblast.dunsmor.com> (raw)
In-Reply-To: <80k46ri112.fsf@somewhere.org> (Sebastien Vauban's message of "Wed, 23 Nov 2011 11:30:33 +0100")
On Wed, Nov 23 2011, Sebastien Vauban wrote:
> Hi Nick,
>
> Nick Dokos wrote:
>> Martyn Jago <martyn.jago@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 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)
I added this to the new worg publishing process. Here's an example of
what the first few lines of output will look like:
--8<---------------cut here---------------start------------->8---
worg publish process 5432 started at 11/30/11@10:01:48
Loading /home/emacs/.emacs.el (source)...
Loading /home/emacs/.emacs-custom.el (source)...
Org-mode 7.7 on Emacs 23.2.1.
Loading /home/emacs/.org-timestamps/worg-org-faq.cache...
Loading vc-git...
Skipping unmodified file /home/emacs/git/worg/org-faq.org
[...]
--8<---------------cut here---------------end--------------->8---
I'll send an email to the list soon about the new worg setup.
Regards,
Jason
next prev parent reply other threads:[~2011-11-30 22:06 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
2011-11-23 15:12 ` Nick Dokos
2011-11-23 15:31 ` Sebastien Vauban
2011-11-30 22:06 ` Jason Dunsmore [this message]
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=87y5uxb702.fsf@riotblast.dunsmor.com \
--to=jasondunsmore@gmail.com \
--cc=emacs-orgmode@gnu.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).