From: henry atting <firstname.lastname@example.org>
To: Nicolas Goaziou <email@example.com>
Cc: firstname.lastname@example.org, henry atting <email@example.com>
Subject: Re: new html exporter
Date: Sun, 30 Sep 2012 12:06:34 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Nicolas Goaziou's message of "Sat, 29 Sep 2012 18:51:51 +0200")
Nicolas Goaziou <firstname.lastname@example.org> writes:
> henry atting <email@example.com> writes:
>> Only a single file. I understand that something like this will no work
>> anymore with the new exporter.
>> #+SETUPFILE: /home/me/.setup.org
> It's #+SETUP_FILE: in the new exporter.
Okay, then it applies the `#+STYLE:' option from the setup file but not
the path to org-info.js set in `#+INFOJS_OPT: path:~/.org-info.js'.
>> Besides I'm pretty happy with the old exporter and was only curious
>> because I read that it will be replaced with the new one in a future
>> stable version. I hope the old one will remain part of contrib (or
>> antique or whatever) so I can choose to my liking.
> It would help to know what the new exporter is missing.
Most probably nothing. Orgmode already has so many features, most of
them I will never need I suppose. I am using orgmode for some years now
but I wouldn't call me a heavy user. I jot down notes with org-capture,
keep up a very simple agenda, plot my monthly household expenses and do
some exporting to html.
As to me I am content with e.g. org-export-as-html as I probably will be
with the upcoming switch to the new exporter. I am only a little
disappointed by the fact that these above mentioned tiny changes (like
setupfile to setup_file) for someone like me (who does not want to
take a deeper look into orgmode) are more confusing than they should be.
Then again this little confusion will of course not discourage me from using
next prev parent reply other threads:[~2012-09-30 10:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-29 11:36 henry atting
2012-09-29 15:18 ` Robert Klein
2012-09-29 16:19 ` henry atting
2012-09-29 16:51 ` Nicolas Goaziou
2012-09-30 10:06 ` henry atting [this message]
2012-09-30 10:29 ` Nicolas Goaziou
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).