From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [ox, patch] Add #+SUBTITLE
Date: Mon, 23 Mar 2015 01:05:21 +0100 [thread overview]
Message-ID: <87y4mo60ji.fsf@gmx.us> (raw)
In-Reply-To: 87lhiotyc7.fsf@wmi.amu.edu.pl
Hi,
First: Please don't take me being critical as meaning I'm necessarily
negative about. I'm just minimizing risk over the expectation.
Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
>> - What happens when you cannot maintain it any longer? Note also that the
>
> Either the project dies, or someone takes it over. The latter seems to
> be quite common in the LaTeX community, so I wouldn't be very worried.
That does not seem like something you'd want to base Org on...
>> scope is somewhat different as a typical latex package solves a problem
>> like "provide good tables" or "enhance itemize 2e" (ei2e). Such
>> packages are fairly easy to replace (e.g. sugfigure → subcaption).
>
> Fair enough. Not a problem imho, though. A “package” has a very wide
> definition in the LaTeX world, and I explained why a package would be
> better than a class (even though doing it as a package would be a bit
> more work with ensuring that it works with wide range of classes).
I am talking about latex packages and the example mentions real latex
packages. A class would be a sure route to failure. A packages is fine.
But it's beside the point. You argue, if I understand correctly, for
amending ox-latex to rely on a very specialized package, which we may or
may not easily be able to replace should it come to that.
>> - I don't want latex code generated by org to a "special flavor" like with
>> LyX.
> In my vision, the huge preamble is replaced by \usepackage{orglatex} or
> something like this, and instead of, say,
OK.
> : \section{{\bfseries\sffamily TODO} hello\hfill{}\textsc{world}}
>
> (how is that not a “special flavor”?) you would have
>
> : \section{\orgtodo{TODO}hello\orgtags{world}}
>
> or, if we decide to do a major surgery on LaTeX’s sectioning mechanism
> (which is debatable), even
>
> : \section[orgtodo=TODO,orgtags=world]{hello}
Both are appealing.
>> - Why can the issues you have in mind not be solved by a specialized
>> derived backend? Such as ox-beamer or ox-koma-letter.
>
> This seems to bug you enough that you basically asked twice;-).
No. Here is ask why you can't settle for another Org-mode backend, rather
than a new latex package. This can even live in contrib without signing
the copyright agreement with FSF.
E.g. you could get a very similar result to what you are talking about by
defining the macros at export-level (e.g. write-out
\providecommand\orgtodo...) and allowed writing a preamble or similar (if
you really mind long preambles). That way anybody would also be able to
customize on the latex end, if they so desire.
> As I said, people use Org-mode in various ways. [...]. For other
> people, [they make] a draft in Org they continue their work in LaTeX
> (...). For them, human-readable (and editable) LaTeX code is a nice
> thing.
Good point.
> Also, adding some options in a LaTeX package seems to have less friction
> than in Org. In the former, you just code it and make a pull request to
> the package maintainer (or send a patch, or even just file a feature
> request). In the latter, you bug Nicolas, and he has to think about the
> impact of your feature request for other backends (because Org is not
> LaTeX-centric!).
I don't see the difference.
—Rasmus
--
You people at the NSA are becoming my new best friends!
next prev parent reply other threads:[~2015-03-23 0:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 23:23 [ox, patch] Add #+SUBTITLE Rasmus
2015-03-21 2:26 ` Marcin Borkowski
2015-03-21 2:32 ` Melanie Bacou
2015-03-22 14:02 ` Nicolas Goaziou
2015-03-22 15:29 ` Rasmus
2015-03-22 20:47 ` Marcin Borkowski
2015-03-22 21:21 ` Thomas S. Dye
2015-03-22 21:23 ` John Williams
2015-03-22 22:43 ` Rasmus
2015-03-22 23:19 ` Marcin Borkowski
2015-03-23 0:05 ` Rasmus [this message]
2015-03-23 8:32 ` Marcin Borkowski
2015-03-23 9:00 ` Sebastien Vauban
2015-03-24 9:05 ` Nicolas Goaziou
2015-03-24 9:37 ` Rasmus
2015-03-28 15:17 ` Nicolas Goaziou
2015-03-26 2:36 ` Melanie Bacou
2015-03-26 2:38 ` Melanie Bacou
2015-03-26 10:10 ` Rasmus
2015-03-22 14:34 ` Eric Abrahamsen
2015-03-22 15:32 ` Rasmus
2015-03-23 1:17 ` Eric Abrahamsen
2015-03-26 2:47 ` Melanie Bacou
2015-03-26 9:52 ` Rasmus
2015-03-26 10:42 ` Rasmus
2015-03-28 8:26 ` Melanie Bacou
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=87y4mo60ji.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).