From: Fabrice Popineau <fabrice.popineau@supelec.fr>
To: Fabrice Popineau <fabrice.popineau@supelec.fr>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Export / LaTeX / suggestion
Date: Tue, 7 May 2013 23:34:56 +0200 [thread overview]
Message-ID: <CAFgFV9OFN0zh-HhT6BKFAjXqpf2E=x_TGUzzzRczEztmU5ppmA@mail.gmail.com> (raw)
In-Reply-To: <87wqrapk29.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]
> I don’t think you want to do that – each backend (latex, html, etc.)
> could have its own incompatible keywords.
You are right. I was thinking of dropping them if they were unkown to the
current backend,
but it is not exactly a solution.
> (I’ve got a solution to this that I’ve been using for the past several
> weeks, but it involves several interlocking pieces and is too messy to
> be shared still. In brief, it comprises extending the parser to handle
> :keywords on a #+begin_foo line, and extending the exporter backends to
> allow different types of block (definition, quote, etc.) to be formatted
> using that information. I’m busy with exams at the moment, but in a
> week or so I hope to have some free time to work on it, among other
> org-related projects.)
LaTeX (and worse beamer) are known to require lots of markup (sometimes
more than actual text).
The real org-mode asset is to remove lots of markup.
Maybe we should just avoid to reintroduce too much of this markup, even if
it is hidden in drawers and so on.
This was a general remark. I'm very interested in reading what you have
been able to achieve.
My primary concern was to be able to fold the #+begin_environment and to be
able to copy/paste it
without having to mark the #+attr_ previous line.
Best regards,
Fabrice
[-- Attachment #2: Type: text/html, Size: 1949 bytes --]
prev parent reply other threads:[~2013-05-07 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 19:42 Export / LaTeX / suggestion Fabrice Popineau
2013-05-07 21:16 ` Aaron Ecay
2013-05-07 21:34 ` Fabrice Popineau [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='CAFgFV9OFN0zh-HhT6BKFAjXqpf2E=x_TGUzzzRczEztmU5ppmA@mail.gmail.com' \
--to=fabrice.popineau@supelec.fr \
--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).