From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: [RFC] About `org-export-with-\(fixed-width\|tables\)'
Date: Wed, 18 Dec 2013 21:36:24 +0100 [thread overview]
Message-ID: <871u1999rr.fsf@gmail.com> (raw)
Hello,
At the moment, `org-export-with-fixed-width' and
`org-export-with-tables' (or their OPTIONS equivalent ::t and |:t) are
broken when not set to their default value. Also, "fixing" them is not
trivial. I think this is a good time to ponder about their usefulness.
Indeed, I don't think anyone would want to remove tables (or fixed-width
areas) from Org syntax. These variables were probably written because
tables and fixed-width can occasionally get in the way, on very specific
lines.
However, Org already provides ways to work around such problems. For
example, a table can be wrapped within an example block, or an offending
line can start with \vert instead of "|".
Therefore, in today's Org, they don't make much sense anymore. As
a consequence, I'd like to either:
1. Remove them completely from code base;
2. Change their meaning so they behave like `org-export-with-toc' or
`org-export-with-tags', that is: when `org-export-with-tables' is
set to nil, all tables are ignored during export.
I don't think option 2 is really useful, but I don't mind either way.
WDYT?
Regards,
--
Nicolas Goaziou
next reply other threads:[~2013-12-18 20:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 20:36 Nicolas Goaziou [this message]
2013-12-18 20:44 ` [RFC] About `org-export-with-\(fixed-width\|tables\)' Nick Dokos
2013-12-18 21:19 ` Rasmus
2013-12-18 21:49 ` Thomas S. Dye
2013-12-18 21:58 ` Nicolas Goaziou
2013-12-18 22:24 ` Thomas S. Dye
2013-12-19 22:08 ` Florian Beck
2014-01-03 15:03 ` Bastien
2014-01-05 0:18 ` Nicolas Goaziou
2014-01-05 6:36 ` Bastien
2014-01-05 17:00 ` Florian Beck
2014-01-05 22:14 ` Nicolas Goaziou
2014-01-04 15:11 ` Eric Abrahamsen
2014-01-07 18:17 ` Eric S Fraga
2014-01-08 7:23 ` Florian Beck
2014-01-08 8:17 ` Eric Abrahamsen
2014-01-08 12:00 ` 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=871u1999rr.fsf@gmail.com \
--to=n.goaziou@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).