From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: Greg Minshall <minshall@umich.edu>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: On zero width spaces and Org syntax
Date: Fri, 03 Dec 2021 20:30:23 +0000 [thread overview]
Message-ID: <877dcl2zz4.fsf@posteo.net> (raw)
In-Reply-To: <4048716.1638558205@apollo2.minshall.org> (Greg Minshall's message of "Fri, 03 Dec 2021 22:03:25 +0300")
Hi Greg, thank you for your comment,
Greg Minshall writes:
> in fact, i am always queasy when i enter ZWNBSP in a .org (or any other)
> file. some sort of "visible" sequence would be great. backwards
> compatibility might be a problem.
Yes I agree. I think that in this case, a new mark would not compromise
backward compatibility, as this presumed new mark would do the same
function as zero width space: i.e. delimit to preserve emphasis. Of
course one could go on using a zero-width space, though I keep thinking
that this is rather a puntual workaround and should not form part of the
syntax.
> your last example
>
> : [''*literature*'']
>
> seems a bit of sleight-of-hand, though. iiuc, text inside square
> brackets isn't highlighted currently, and ZWNBSP doesn't (afaict) turn
> on highlighting. (maybe there's been recent discussion, modifications
> of this?)
The idea would be to use a kind of 'protection mark', to allow something
in a context where it is not allowed: a passport ;-). As the emphasis
marks are recognized before and after a single quote, I thought that
maybe a sequence of two single quotes could function here as a
protection mark (screenshot: https://i.imgur.com/cPIH9qa.png). For
example:
#+begin_example
| Some examples where emphasis marks are not allowed | Protected emphasis marks |
|----------------------------------------------------+--------------------------|
| /meta/literature | /meta/''literature |
| [/literature/] | [''/literature/''] |
| <*literature*> | <''*literature*''> |
| meta/*literature* | meta/''*literature* |
#+end_example
With the protection marks we get (in LaTeX for example):
\emph{meta}literature
[\emph{literature}]
<\textbf{literature}>
meta/\textbf{literature}
Best regards,
Juan Manuel
next prev parent reply other threads:[~2021-12-03 20:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 12:48 On zero width spaces and Org syntax Juan Manuel Macías
2021-12-03 19:03 ` Greg Minshall
2021-12-03 20:30 ` Juan Manuel Macías [this message]
2021-12-03 21:48 ` Tim Cross
2021-12-04 1:26 ` Juan Manuel Macías
2021-12-04 4:04 ` Tom Gillespie
2021-12-04 5:29 ` Juan Manuel Macías
2021-12-04 15:26 ` Max Nikulin
2021-12-04 20:29 ` Tim Cross
2021-12-06 11:40 ` Eric S Fraga
2021-12-04 6:43 ` Marcin Borkowski
2021-12-04 7:22 ` Ihor Radchenko
2021-12-04 17:37 ` Marcin Borkowski
2021-12-06 16:01 ` Robert Pluim
2021-12-06 16:42 ` Greg Minshall
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=877dcl2zz4.fsf@posteo.net \
--to=maciaschain@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=minshall@umich.edu \
/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).