Nick Dokos writes:
> The problem is that these things are configurable, so the above is onlyu
> true by default. But you can redefine `org-emphasis-regexp-components` in
> ways that would make the above untrue: hence the more abstract description.
They are no longer configurable:
;; This used t
Jens Lechtenboerger writes:
> Actually, what about this? Get rid of both, BORDER and BODY, and
> specify CONTENTS as follows:
> “Either a string (when MARKER represents code or verbatim) or a
> series of objects from the standard set, not spanning more than
> three lines. In any case, CONTENTS
On Wed, Dec 07, 2022 at 11:29:29AM +0100, Jens Lechtenboerger wrote:
> On 2022-12-07, Timothy wrote:
[...]
> > This seems like an improvement to me, implemented in 56338725e61 :)
>
> Many thanks, Timothy!
Seconded :)
--
t
signature.asc
Description: PGP signature
On 2022-12-07, Timothy wrote:
> Hi Jens,
>
>> Actually, what about this? Get rid of both, BORDER and BODY, and
>> specify CONTENTS as follows:
>> “Either a string (when MARKER represents code or verbatim) or a
>> series of objects from the standard set, not spanning more than
>> three lines. In
Hi Jens,
> Actually, what about this? Get rid of both, BORDER and BODY, and
> specify CONTENTS as follows:
> “Either a string (when MARKER represents code or verbatim) or a
> series of objects from the standard set, not spanning more than
> three lines. In any case, CONTENTS must neither begin n
On 2022-12-07, Jens Lechtenboerger wrote:
> On 2022-12-07, Max Nikulin wrote:
>
>> On 07/12/2022 01:28, 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
On 2022-12-07, Max Nikulin wrote:
> On 07/12/2022 01:28, 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 r
On 07/12/2022 01:28, 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?
I thin
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 he
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,
10 matches
Mail list logo
