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, 15 Sep 2010 09:12:37 -0500 [thread overview]
Message-ID: <AANLkTinvefMZtEoLxqXApYytx+ZpMz2xiBK3Ju_xgFGZ@mail.gmail.com> (raw)
In-Reply-To: <87k4mn1ayu.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 1362 bytes --]
On Wed, Sep 15, 2010 at 6:51 AM, Bastien <bastien.guerry@wikimedia.fr>wrote:
> John Hendy <jw.hendy@gmail.com> writes:
>
> > Working on it... if you notice there are broken-linked images right
> > now.
>
> The links are not broken anymore.
>
> I made a small change on Worg's setup: now images can simply be put in
> the same directory than files linking to them, and they will be exported
> in this very directory.
>
>
The images are indeed there. Thanks!
Should this be the standard practice now? Images for something in
Worg/org-contrib/babel/languages/ob-doc_*.org should be kept in the same
directory?
Also, is there a list of the directories that are published and those that
are not? For example, I also put a downloadable example file here:
http://orgmode.org/worg/org-contrib/babel/examples/org-babel-gnuplot.org
It's in the same place as the downloadable file for org-plot (
http://orgmode.org/worg/org-tutorials/org-plot.org). org-plot.org is active
but org-babel-gnuplot.org is not...
I'm just wondering if the Worg instructions on how to contribute should
include a directory tree of some sort so that the newer contributors like
myself are on the same page as everyone else?
Thanks for the assistance,
John
> HTH,
>
> PS: We use to be images on the Worg/images/ directory but I don't think
> this is really necessary.
>
> --
> Bastien
>
[-- Attachment #1.2: Type: text/html, Size: 2328 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
next prev parent reply other threads:[~2010-09-15 14:12 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 [this message]
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
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=AANLkTinvefMZtEoLxqXApYytx+ZpMz2xiBK3Ju_xgFGZ@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).