From: Ihor Radchenko <yantar92@gmail.com>
To: David Boss <dave.boss@yahoo.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Maybe not as simple as I thought
Date: Wed, 03 Aug 2022 20:21:08 +0800 [thread overview]
Message-ID: <87edxxikln.fsf@localhost> (raw)
In-Reply-To: <639971559.598159.1657652027758@mail.yahoo.com>
David Boss <dave.boss@yahoo.com> writes:
> If, asI have understood, there is a single zero-width-space character I canuse to stop Org mode interpretation, don't tell me how to insert it;tell me its 8-bit value, in binary or hex. If I have to be in16-bit-character mode to use it, tell me that.
>
> If it's really 2 characters, but works OK in 8-bit mode, tell methat, too, and tell me the 16 bits.
zero-width space is a UTF character.
> Next, if that character appears in a file, exactly what effectdoes it have on the Org mode interpreter? Does it
> suppress the Org-mode-syntactical effect of the precedingcharacter? Or,
>
> suppress the syntactical effect of the following character?Or,
>
> only work if it appears both before and after its intended victim?
It has the same effect as inserting an actual space in place of the
zero-width space, except that zero-width space does not create an actual
space between the characters.
> Absolutely all I want to be able to do, is to find stars, slashes,and underlines, in incoming text, and add something to each to keepit from being interpreted by the Org mode interpreter. Using lispcode, not my fingers.
>
> I don't need to be told anything else.
Another alternative is using entities:
* = \star
/ = \slash
_ = \under
Entities will never be interpreted as markup boundaries.
Best,
Ihor
prev parent reply other threads:[~2022-08-03 12:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <639971559.598159.1657652027758.ref@mail.yahoo.com>
2022-07-12 18:53 ` Maybe not as simple as I thought David Boss
2022-08-03 12:21 ` Ihor Radchenko [this message]
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=87edxxikln.fsf@localhost \
--to=yantar92@gmail.com \
--cc=dave.boss@yahoo.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).