From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Gunnar Wolf <gwolf@gwolf.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: [new exporter] Guides on what incompatibilities to watch for?
Date: Wed, 20 Feb 2013 08:21:34 +0000 [thread overview]
Message-ID: <87bobf9z01.fsf@ucl.ac.uk> (raw)
In-Reply-To: <20130219175703.GC130669@gwolf.org> (Gunnar Wolf's message of "Tue, 19 Feb 2013 11:57:03 -0600")
Gunnar Wolf <gwolf@gwolf.org> writes:
> Hi,
>
> I'm not very specific in this mail, but am wondering…
>
> I have some nontrivial documents written in Org-mode. My main use case
> for Org is mostly to author texts, rather than using its time-tracking
> features. I fear that with the new exporter, several of my documents'
> features will no longer work or -worse- be interpretted differently,
> having a negative impact in my output.
Don't worry too much. I had the same worry because although I do use
the time tracking (GTD) feature of org extensively, the majority of the
time I am using org is for writing. Although there are some changes you
will need to make to your documents, the number of changes will depend
on the export target(s) and your use of figures and tables, say. Others
in this thread have already pointed you to the docs that are available.
You don't actually say what the export target(s) you use is/are. In my
case, most of my export to latex/pdf documents required minimal changes
and only to figure attributes basically. My beamer slides required more
significant changes but, even here, the impact was much less dramatic
than I had expected and worried about! And, quite importantly, the
beamer exporter is now more logical, in my opinion.
Don't panic (TM)! ;-)
--
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org 7.9.3e-1140-g272ca4
prev parent reply other threads:[~2013-02-20 8:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 17:57 [new exporter] Guides on what incompatibilities to watch for? Gunnar Wolf
2013-02-19 19:04 ` Suvayu Ali
2013-02-19 19:38 ` Bastien
2013-02-19 19:11 ` Thomas S. Dye
2013-02-20 8:21 ` Eric S Fraga [this message]
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=87bobf9z01.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=gwolf@gwolf.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).