From: Kaushal Modi <kaushal.modi@gmail.com>
To: emacs-org list <emacs-orgmode@gnu.org>,
Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Escape mechanism in code and verbatim blocks
Date: Sat, 19 Sep 2015 09:37:16 -0400 [thread overview]
Message-ID: <CAFyQvY05MuKcqh20L79oa=MC1ukJw6_LmdaXnO72VMjY6nGC1Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]
@Nicolas
I am with you on not using non-ascii characters to escape stuff.
I like your proposal about escaping in code and verbatim blocks.
--
Kaushal Modi
On Sep 19, 2015 7:35 AM, "Nicolas Goaziou" <mail@nicolasgoaziou.fr> wrote:
> Kaushal Modi <kaushal.modi@gmail.com> writes:
>
> > My most common uses are escaping double quotes (") and equals (=) within
> > org verbatim blocks (=VERBATIM=)
> >
> > Examples:
> >
> > 1. =var=[ZWS]val=
> > 2. =[ZWS]"something"[ZWS]=
> >
> > Here [ZWS] is the 0x200b zero width space unicode char.
> >
> > I found [ZWS] useful as a generic escape char for org mode. There are few
> > other cases where this has been useful, but I can't recall right now.
> >
> > In any case, what would be the recommended way to escape " and = in the
> > above 2 examples?
>
> As I said, entities can only escape most Org syntax. Verbatim and code
> objects are an exception. Here I think we should introduce an escape
> mechanism, much like the one used in macro arguments in order to escape
> commas.
>
> For example, in a verbatim object, one only needs to escape "=", using
> common "\". Obviously, "\=" constructs can be escaped with "\\=" and so
> on. Likewise, in code objects, only "~" needs to be escaped.
>
> In any case, I don't think Org syntax should rely on non-ASCII
> characters.
>
> Regards,
>
[-- Attachment #2: Type: text/html, Size: 1908 bytes --]
reply other threads:[~2015-09-19 13:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAFyQvY05MuKcqh20L79oa=MC1ukJw6_LmdaXnO72VMjY6nGC1Q@mail.gmail.com' \
--to=kaushal.modi@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).