From: timor <timor.dd@gmail.com>
To: mail@nicolasgoaziou.fr
Cc: emacs-orgmode@gnu.org
Subject: Re: Show presence of zero width spaces using overlay
Date: Tue, 19 Apr 2016 13:38:28 +0200 [thread overview]
Message-ID: <CAAX25XCAyKXC0fkp0F53eFbKbvcHKT=JgDiyvwBQVCp3S_wUNQ@mail.gmail.com> (raw)
Hello Nicolas,
2016-04-19 12:16 GMT+02:00 Nicolas Goaziou <mail@nicolasgoaziou.fr>:
> Actually, this is not really a specification of the problem, which is
> quite tricky. The list of characters is but one part of it. Another part
> is where escaping should be allowed. Note that allowing to escape
> everywhere would be terrible, if only performance-wise. The last part is
> about handling it at the parser level (there's also the fontification,
> which doesn't use the parser ATM).
Good points. I don't understand enough org mode internals to judge
how much effort is needed on which level for things like this.
Maybe it is viable to start defining and implementing some obvious
cases, which can later be generalized into a rule, so that code has
not to be rewritten on every level at once.
In light of this, I can think of defining the case that bugged me the
most like this:
In plain-text parts of org documents (i.e. that would be exported as
the content of <p> attributes in html, or to plain text paragraphs in
Markdown, etc.), there shall be a way to treat strings in the same way
as the surrounding plain text, which would otherwise be handled by
org-mode in a special way.
Does that help?
regards,
timor
next reply other threads:[~2016-04-19 11:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 11:38 timor [this message]
2016-04-19 19:21 ` Show presence of zero width spaces using overlay Nicolas Goaziou
2016-04-19 23:20 ` timor
-- strict thread matches above, loose matches on Subject: below --
2015-09-22 15:13 timor
2015-09-27 9:41 ` Nicolas Goaziou
2016-04-19 9:23 ` timor
2016-04-19 10:16 ` Nicolas Goaziou
2015-09-18 18:44 Kaushal Modi
2015-09-18 21:11 ` Nicolas Goaziou
2015-09-18 22:39 ` Kaushal Modi
2015-09-19 1:47 ` Eric Abrahamsen
2015-09-19 4:07 ` Kaushal Modi
2015-09-19 4:11 ` Kaushal Modi
2015-09-19 6:15 ` Kaushal Modi
2015-09-19 7:22 ` Eric Abrahamsen
2015-09-19 13:46 ` Kaushal Modi
2015-09-19 11:37 ` Nicolas Goaziou
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='CAAX25XCAyKXC0fkp0F53eFbKbvcHKT=JgDiyvwBQVCp3S_wUNQ@mail.gmail.com' \
--to=timor.dd@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).