emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Thomas S. Dye" <tsd@tsdye.com>
To: Jason Dunsmore <emacs-orgmode@dunsmor.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Worg updating?
Date: Fri, 18 Mar 2011 05:55:26 -1000	[thread overview]
Message-ID: <739E73AE-E86A-4B3E-88A0-61F08A789FAB@tsdye.com> (raw)
In-Reply-To: <87ipvhqgsc.fsf@riotblast.dunsmor.com>

Thanks Jason,

Worg is magical.

All the best,
Tom

On Mar 17, 2011, at 4:54 PM, Jason Dunsmore wrote:

> Erik Iverson <eriki@ccbr.umn.edu> writes:
>
>> On 03/17/2011 05:34 PM, Nick Dokos wrote:
>>> Thomas S. Dye<tsd@tsdye.com>  wrote:
>>>
>>>> Aloha all,
>>>>
>>>> Changes I made to the LaTeX export tutorial several days ago  
>>>> haven't
>>>> made their way to Worg yet.  Is Worg updating?
>>>>
>>>> All the best,
>>>> Tom
>>>>
>>>
>>> Thanks for reminding me: I made a change to org-hacks some time  
>>> ago and it
>>> hasn't shown up yet.  Maybe it would be a good idea to timestamp  
>>> pages
>>> with the update time?
>>>
>>> Does Worg contain any information on how Worg is built? I found
>>>
>>>   http://orgmode.org/worg/sources/
>>
>> See:
>>
>> http://orgmode.org/worg/worg-setup.html
>>
>> which will direct you to:
>>
>> http://orgmode.org/worg/publishing.txt
>>
>> AT the bottom of that file:
>>
>> "Generating tree-style sitemap for Sitemap for project worg-pages
>> Not a standard Org-mode time string: 2010.08.25 20:41:52"
>
> This and another badly formatted date were causing the Worg publishing
> process to fail.  I fixed it in these two commits:
>
> http://repo.or.cz/w/Worg.git/commitdiff/cba1f50f636401723c6bf9c38d86e725817123ff
> http://repo.or.cz/w/Worg.git/commitdiff/a5ba2e96757d7b5870f667f9bd23c9491bd9f14e
>
> Thomas' new section is now present after republishing Worg:
>
> http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-10_1
>
> Regards,
> Jason
>

  parent reply	other threads:[~2011-03-18 15:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17 20:53 Worg updating? Thomas S. Dye
2011-03-17 22:34 ` Nick Dokos
2011-03-17 22:55   ` Erik Iverson
2011-03-18  2:54     ` Jason Dunsmore
2011-03-18  3:55       ` Nick Dokos
2011-03-18  4:56         ` Nick Dokos
2011-03-18 15:55       ` Thomas S. Dye [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-09-17 16:32 Tom Dye
2010-09-17 17:10 ` John Hendy
2010-09-17 17:56   ` Erik Iverson
     [not found]     ` <87tylo2pnp.fsf@gmail.com>
2010-09-17 18:55       ` Bastien
2010-09-18 17:53         ` Bastien
2010-09-18 18:39           ` Tom Dye
2010-09-19 18:25             ` Bastien
2010-09-19 19:43               ` Tom Dye
2010-09-19 20:48                 ` Bastien
2010-09-18 18:06         ` Bastien
2010-09-19 21:31     ` 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=739E73AE-E86A-4B3E-88A0-61F08A789FAB@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@dunsmor.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \
    /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).