emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Bastien <bastien.guerry@wikimedia.fr>
Cc: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>, emacs-orgmode@gnu.org
Subject: Re: Re: Babel+gnuplot on Worg
Date: Wed, 22 Sep 2010 09:38:26 -0500	[thread overview]
Message-ID: <AANLkTikK+2CoctD_VCpskGFWf3RiXG7g+hDd5mvqBBka@mail.gmail.com> (raw)
In-Reply-To: <878w2thmq9.fsf@gnu.org>


[-- Attachment #1.1: Type: text/plain, Size: 1035 bytes --]

AH! Perfect. So, the procedure is:

- put them wherever you want
- all sources are put in a source directory in addition to their published
content
- link to them via orgmode/worg/sources

One question, then... I've tailored the raw org-mode copy to be slightly
different than the tutorial I created. Is it possible to have a file pass an
option to not be published in #+options or elsewhere? Say I want it put in
sources for download but don't want it to get it's own .php page on worg --
is that possible?


John

On Wed, Sep 22, 2010 at 9:33 AM, Bastien <bastien.guerry@wikimedia.fr>wrote:

> John Hendy <jw.hendy@gmail.com> writes:
>
> > Trying to update worg-setup.org but am not finding the worg/sources
> directory
> > you're referring to.
>
> The http://orgmode.org/worg/sources/ is only on the server, not on the
> Worg repository.
>
> All .org files from the repo are automatically uploaded to this sources/
> directory on the server.
>
> See this :
>
>  http://orgmode.org/worg/sources/emacs.el
>
> HTH,
>
> --
>  Bastien
>

[-- Attachment #1.2: Type: text/html, Size: 1775 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-09-22 14:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-10 15:49 Babel+gnuplot on Worg John Hendy
2010-09-10 16:52 ` d.tchin
2010-09-10 18:47   ` John Hendy
2010-09-10 19:33     ` d.tchin
2010-09-14  9:55 ` Sébastien Vauban
2010-09-14 13:57   ` John Hendy
2010-09-15 11:51     ` Bastien
2010-09-15 14:12       ` John Hendy
2010-09-19 21:31         ` Bastien
2010-09-20 15:00           ` John Hendy
2010-09-20 21:07             ` Bastien
2010-09-20 21:15               ` John Hendy
2010-09-20 21:20                 ` Bastien
2010-09-22 14:29                   ` John Hendy
2010-09-22 14:33                     ` Bastien
2010-09-22 14:38                       ` John Hendy [this message]
2010-09-20 15:07           ` John Hendy
2010-09-20 18:08             ` Thomas S. Dye
2010-09-22 14:45               ` John Hendy
2010-09-22 16:07                 ` Thomas S. Dye

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=AANLkTikK+2CoctD_VCpskGFWf3RiXG7g+hDd5mvqBBka@mail.gmail.com \
    --to=jw.hendy@gmail.com \
    --cc=bastien.guerry@wikimedia.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=wxhgmqzgwmuf@spammotel.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).