From: "Clément Pit--Claudel" <clement.pit@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Bug? Highlighting inconsistent with export
Date: Mon, 29 Aug 2016 13:52:08 -0400 [thread overview]
Message-ID: <db368413-6487-fa6e-726a-6e84e7af1640@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1077 bytes --]
Hi all,
In the following snippets, I have marked which bits are syntax-highlighted as code, and which bits are exported as code.
Some “=code=” [fn:: ~more~ ~of it~]. ~even more code~— ~this~ —.
Highlighted? No Yes No No No
Exported? No Yes Yes No No
Note the inconsistency in the footnote case. ~this~ isn't highlighted because it's surrounded by non-breaking space. ~of it~ isn't highlighted because of the ‘]’, but on export it does get rendered as code.
Some suggestions: Paired delimiters and quotes, such as “” ‘’ <> [], could be allowed around code (by changing the default for ‘org-emphasis-regexp-components’). Spaces (including zero-width spaces) could also be allowed: this would provide a universal mechanism for ensuring that a bit of code is highlighted. For example, “There are many ~let~s in this code” wouldn't work, but “There are many ~let~s in this code” would work fine.
Cheers,
Clément.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2016-08-29 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 17:52 Clément Pit--Claudel [this message]
2016-08-30 10:08 ` Bug? Highlighting inconsistent with export Nicolas Goaziou
2016-08-30 16:36 ` Clément Pit--Claudel
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=db368413-6487-fa6e-726a-6e84e7af1640@gmail.com \
--to=clement.pit@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).