From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: emphasis borders, double quotes, and export
Date: Fri, 28 Mar 2014 16:10:27 +0100 [thread overview]
Message-ID: <m2txai2wbg.fsf@polytechnique.org> (raw)
In-Reply-To: <m2y4zutogf.fsf@polytechnique.org> (Alan Schmitt's message of "Fri, 28 Mar 2014 14:58:08 +0100")
Alan Schmitt <alan.schmitt@polytechnique.org> writes:
> Hello,
>
> I have removed the single and double quote characters from my
> configuration of the emphasis borders:
>
> #+begin_src emacs-lisp
> (setcar (nthcdr 2 org-emphasis-regexp-components) " \t\n,")
> (custom-set-variables `(org-emphasis-alist ',org-emphasis-alist))
> #+end_src
>
> However, the latex export of the following file is not correct.
>
> This is a string: ~"Nil"~.
>
> The generated latex is as follows (I show just the fragment of
> interest):
>
> #+begin_src latex
> This is a string: \textasciitilde{}"Nil"\textasciitilde{}.
> #+end_src
>
> I see the same problem with html export.
>
> Note that syntax highlighting works correctly.
>
> Is this a bug?
Looking a little deeper into this, it seems to be a regression. I had
files with things like ~'a list~ that exported correctly a couple weeks
ago that no longer export correctly.
Alan
next prev parent reply other threads:[~2014-03-28 15:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 13:58 emphasis borders, double quotes, and export Alan Schmitt
2014-03-28 15:10 ` Alan Schmitt [this message]
2014-03-28 16:29 ` Nicolas Goaziou
2014-03-28 17:22 ` Alan Schmitt
2014-04-04 13:08 ` Alan Schmitt
2014-04-04 19:02 ` Nicolas Goaziou
2014-04-04 21:52 ` Nick Dokos
2014-04-04 22:35 ` Nicolas Goaziou
2014-04-05 3:04 ` Nick Dokos
2014-04-05 9:41 ` Alan Schmitt
2014-04-05 10:17 ` Nicolas Goaziou
2014-04-06 14:00 ` Alan Schmitt
2014-04-06 14:13 ` Nicolas Goaziou
2014-04-06 19:04 ` Alan Schmitt
2014-04-06 19:37 ` Nicolas Goaziou
2014-04-06 21:34 ` Nick Dokos
2014-04-07 12:57 ` Alan Schmitt
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2txai2wbg.fsf@polytechnique.org \
--to=alan.schmitt@polytechnique.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.