Re: [PATCH] Add backslash to list of POST characters for text markup

[Tom Alexander]

Thanks!

--
Tom Alexander
pgp: https://fizz.buzz/pgp.asc

On Fri, Sep 22, 2023, at 5:29 AM, Ihor Radchenko wrote:
> "Tom Alexander"  writes:
>
>> Backslash appears to be supported. To test I used the following test 
>> document:
>> ```
>> foo ~bar~\& baz
>> ```
>
> Thanks!
> You are right.
> Applied, onto master, with minor amendments to the commit message.
> https://git.sr.ht/~bzg/worg/commit/ba6cda89
>
> -- 
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at .
> Support Org development at ,
> or support my work at 

Re: [PATCH] Add backslash to list of POST characters for text markup

[Ihor Radchenko]

"Tom Alexander"  writes:

> Backslash appears to be supported. To test I used the following test document:
> ```
> foo ~bar~\& baz
> ```

Thanks!
You are right.
Applied, onto master, with minor amendments to the commit message.
https://git.sr.ht/~bzg/worg/commit/ba6cda89

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

[PATCH] Add backslash to list of POST characters for text markup

[Tom Alexander]

Backslash appears to be supported. To test I used the following test document:
```
foo ~bar~\& baz
```

This happens in a document in worg: 
https://git.sr.ht/~bzg/worg/tree/ae64e1a54185232d4ebdcab174d8d4319ffd564d/org-release-notes.org#L

The ampersand was chosen for the test document since that is not a supported 
POST character, to make sure backslash was not simply escaping the next 
character.

In the documentation I wrote out the word "backslash" in parenthesis to 
disambiguate between backslash and escaping the following comma.

Patch is attached.

--
Tom Alexander
pgp: https://fizz.buzz/pgp.ascFrom 098434680b5e3942acc00684a47389f2cdab6208 Mon Sep 17 00:00:00 2001
From: Tom Alexander 
Date: Thu, 21 Sep 2023 21:14:33 -0400
Subject: [PATCH] Add backslash to list of POST characters for text markup.

Backslash appears to be supported. To test I used the following test document:
```
foo ~bar~\& baz
```
The ampersand was chosen since that is not a supported POST character, to make sure backslash was not simply escaping the next character.

In the documentation I wrote out the word "backslash" in parenthesis to disambiguate between backslash and escaping the following comma.
---
 org-syntax.org | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/org-syntax.org b/org-syntax.org
index c5299741..8f0f9b0c 100644
--- a/org-syntax.org
+++ b/org-syntax.org
@@ -249,9 +249,9 @@ discarded.  This also applies to single-line elements.
 
 :This paragraph will not contain
 :a long sequence of spaces before "a".
-: 
+:
 :This paragraph does not have leading spaces according to the parser.
-: 
+:
 :#+begin_src emacs-lisp
 :  (+ 1 2)
 :#+end_src
@@ -1742,7 +1742,7 @@ whitespace characters.
   verbatim) or a series of objects from the standard set. In both
   cases, CONTENTS may not begin or end with whitespace.
 + [[#Special_Tokens][POST]] :: Either a whitespace character, =-=, =.=, =,=, =;=, =:=, =!=, =?=, ='=, =)=, =}=,
-  =[=, ="=, or the end of a line.
+  =[=, ="=, =\= (backslash), or the end of a line.
 
 *Examples*
 
-- 
2.42.0