emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: <tomas@tuxteam.de>
To: emacs-orgmode@gnu.org
Subject: Re: Syntax question: What is BORDER in 4.17. Text Markup?
Date: Tue, 6 Dec 2022 19:54:11 +0100	[thread overview]
Message-ID: <Y4+P02fColFJoSLb@tuxteam.de> (raw)
In-Reply-To: <87mt80e69n.fsf@wi.uni-muenster.de>

[-- Attachment #1: Type: text/plain, Size: 865 bytes --]

On Tue, Dec 06, 2022 at 07:28:20PM +0100, Jens Lechtenboerger wrote:
> Hi there,
> 
> the syntax for Text Markup such as *bold* at [1] specifies
> PRE MARKER CONTENTS MARKER POST with
> CONTENTS as BORDER BODY BORDER and
> BORDER as “Any non-whitespace character.”
> 
> What is the role of BORDER here?  Does it really exist?
> 
> What is BORDER if CONTENTS should be a single character, e.g., in
> the two strings “*x*” and “~*~”?  Are single characters forbidden?

Yes, this seems a bit unfortunate. The BORDER char may be identical
to the BODY. So *f* and *ff* are both valid markups.

Perhaps it'd be clearer to forget about the BORDER, only talk about
BODY and say that BODY is not empty and doesn't start or end with
a whitespace character.

Cheers

> [1] https://orgmode.org/worg/org-syntax.html#Emphasis_Markers

-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2022-12-06 18:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06 18:28 Syntax question: What is BORDER in 4.17. Text Markup? Jens Lechtenboerger
2022-12-06 18:54 ` tomas [this message]
2022-12-07  3:35 ` Max Nikulin
2022-12-07  7:16   ` Jens Lechtenboerger
2022-12-07  7:54     ` Jens Lechtenboerger
2022-12-07  9:36       ` Timothy
2022-12-07 10:29         ` Jens Lechtenboerger
2022-12-07 10:38           ` tomas
2022-12-07 15:43       ` Nick Dokos
2022-12-07 15:52         ` Ihor Radchenko

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=Y4+P02fColFJoSLb@tuxteam.de \
    --to=tomas@tuxteam.de \
    --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).