From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [new exporter] Guides on what incompatibilities to watch for?
Date: Tue, 19 Feb 2013 20:04:18 +0100 [thread overview]
Message-ID: <20130219190418.GG5588@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <20130219175703.GC130669@gwolf.org>
On Tue, Feb 19, 2013 at 11:57:03AM -0600, Gunnar Wolf wrote:
> 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.
>
> Is there a guide on what items should I mostly watch for (or even
> better, what syntax changes should I make) to get my results as
> similar as possible to what I had beforehand?
>
> I am not yet running with the new release; as I follow the Debian
> packaging, I'll rather wait until it "lands" in my system. Still, I
> want to prepare and not let this get me off-guard!
>
Take a look here:
<http://orgmode.org/worg/org-faq.html#new-exporter-switch>
Apart from that I know about the following changes in syntax (to the
best of my knowledge):
1. Attribute lines now take plists
: #+attr_latex :width "5cm"
: #+attr_beamer :options "width=5cm"
2. Beamer backend now interprets nested headline levels as blocks
instead of lists. For some preliminary guidance you can look at
this:
<http://orgmode.org/worg/org-tutorials/org-beamer/org-e-beamer.html>.
Hope this helps,
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2013-02-19 19:04 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 [this message]
2013-02-19 19:38 ` Bastien
2013-02-19 19:11 ` Thomas S. Dye
2013-02-20 8:21 ` Eric S Fraga
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=20130219190418.GG5588@kuru.dyndns-at-home.com \
--to=fatkasuvayu+linux@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).