From: "Chris wallace" <crassshed@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Fwd: Re: [David O'Toole] Fwd: Re: org-publish future ?
Date: Tue, 6 Jun 2006 17:02:52 +0100 [thread overview]
Message-ID: <9bcdfad70606060902i30c11ecav99a21966a6fc14cf@mail.gmail.com> (raw)
In-Reply-To: <9bcdfad70606060901q52c0097fgde12d5d6ffcf83e9@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1713 bytes --]
Apologies, sent this just to Michael and not the whole list:
---------- Forwarded message ----------
From: Chris wallace <crassshed@gmail.com>
Date: 06-Jun-2006 17:01
Subject: Re: [Emacs-orgmode] Re: [David O'Toole] Fwd: Re: org-publish future
?
To: Michael Olson <mwolson@gnu.org>
On 06/06/06, Michael Olson <mwolson@gnu.org> wrote:
> Carsten Dominik <dominik@science.uva.nl> writes:
>
> > Yes, this is certainly true. ascii-to-xxx converters can certainly
> > help you to write your first LaTeX document. However, they don't
> > encourage to grow into that language at all, so to some extend they
> > are a dead end.
>
> I disagree. It would give people an excellent foundation that they
> can build upon, since they can examine the output from that publishing
> routine to learn LaTeX. When they come across limitations of the
> current LaTeX publishing implementation, they will search for
> supplemental information.
If it's really needed, why not just add a faq:
Q: how do I generate laTeX from org?
A: use org-export-to-html and then call html2latex on the result (see
http://html2latex.sourceforge.net/)
?
Chris.
PS. On the subject of org-publish (sort of), one of the things I like most
about org-mode is that I can have Readme.org files scattered over a number
of directories and have them all included in the agenda. However,
org-publish assumes all org files for a single project reside in a single
directory. I wonder if I am the only one who has several directories per
project?
I have hacked org-publish.el (badly) to allow me to supply a list of org
files instead of a directory. If this would be useful for anyone else, I'm
happy to have a go a cleaning it up and offer a patch.
[-- Attachment #1.2: Type: text/html, Size: 2841 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2006-06-06 16:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 21:19 [David O'Toole] Fwd: Re: org-publish future ? David O'Toole
2006-06-06 10:29 ` Carsten Dominik
2006-06-06 10:48 ` David O'Toole
2006-06-06 13:54 ` Michael Olson
2006-06-06 14:17 ` Carsten Dominik
2006-06-06 14:38 ` Michael Olson
[not found] ` <9bcdfad70606060901q52c0097fgde12d5d6ffcf83e9@mail.gmail.com>
2006-06-06 16:02 ` Chris wallace [this message]
2006-06-07 13:06 ` Carsten Dominik
2006-06-07 15:00 ` Chris wallace
2006-06-07 15:25 ` David O'Toole
2006-06-10 12:24 ` Bastien
2006-06-07 17:09 ` Christian Schlauer
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=9bcdfad70606060902i30c11ecav99a21966a6fc14cf@mail.gmail.com \
--to=crassshed@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).