From: Kaushal Modi <kaushal.modi@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Amos Bird <amosbird@gmail.com>, emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Allow more export options to be controlled per-subtree
Date: Thu, 28 Sep 2017 19:25:03 +0000 [thread overview]
Message-ID: <CAFyQvY2LGmgX3pB=xg8iU3soiFdpBjXPt4oYvcf=Oqy5c4serw@mail.gmail.com> (raw)
In-Reply-To: <87zi9emy0m.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
On Thu, Sep 28, 2017 at 3:19 PM Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> I already answered to this problem. Use \star instead of *. It seems
> sub-optimal to prevent any emphasis markup because of a single
> problematic character.
>
OK.
> I mean this variable doesn't solve any problem. If one doesn't want Org
> syntax to interfere with their contents in any way, then Org mode may
> not be the appropriate major mode for the task.
>
I haven't personally needs to set this variable to nil, so I sort of agree
with you.
Therefore, I said that, AFAIC, this variable could as well go away. From
> my point of view, making it more prominent is counter-productive.
>
> In the same category, there is `org-export-with-tables'.
>
Haven't used this one either.
> By the way, it is already possible to prevent emphasis in a subtree
> export:
>
> * Subtree
> :PROPERTIES:
> :EXPORT_OPTIONS: *:nil
> :END:
>
I didn't know that. This solves all the problems. Thanks.
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 1911 bytes --]
next prev parent reply other threads:[~2017-09-28 19:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 17:28 Allow more export options to be controlled per-subtree Kaushal Modi
2017-09-28 18:40 ` Kaushal Modi
2017-09-28 18:47 ` Nicolas Goaziou
2017-09-28 18:59 ` Kaushal Modi
2017-09-28 19:19 ` Nicolas Goaziou
2017-09-28 19:25 ` Kaushal Modi [this message]
2017-09-30 4:59 ` Kaushal Modi
2017-09-30 5:44 ` Amos Bird
2017-09-30 12:13 ` Kaushal Modi
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='CAFyQvY2LGmgX3pB=xg8iU3soiFdpBjXPt4oYvcf=Oqy5c4serw@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=amosbird@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).