On Saturday, October 24, 2020 at 12:46:49 AM UTC+2, TonyM wrote:
>
> Mario,
>
> So ⠪.class:param Braille 246 and Braille 2345⠞ may be an option.
>>
>>
> I understand open and close needs to be asymmetric to see which is which.
> But the solution such as
> /glyph content glyph/ - inline
> or
>
Mario,
So ⠪.class:param Braille 246 and Braille 2345⠞ may be an option.
>
>
I understand open and close needs to be asymmetric to see which is which.
But the solution such as
/glyph content glyph/ - inline
or
glyph content /glyphline - para or block
Still retains a degree of symmetry and is
On Friday, October 23, 2020 at 1:06:15 PM UTC+2, PMario wrote:
Writing all the above text I was thinking: . . . .
>
> What about: *_symbol.class.class:param:param some text__ _ some more
> text__*
>
hmmm.
It doesn't work out with a "single" start char. Way to many problems with
TW
On Friday, October 23, 2020 at 1:28:39 PM UTC+2, PMario wrote:
*Pragma Comment*
>
> Could be
>
> \\ comment comes here till the end of the line
>
>
We are lucky :)
> \\ If pragma comments are used here they are faster as used in the define
> block.
> \\ This comment doesn't produce a
On Friday, October 23, 2020 at 1:06:15 PM UTC+2, PMario wrote:
Writing all the above text I was thinking: . . . .
>
> What about: *_symbol.class.class:param:param some text__ _ some more
> text__*
>
IF:
\customize inline="_" _element="u" ... is a default global definition it
will do the
On Thursday, October 22, 2020 at 1:53:41 PM UTC+2, @TiddlyTweeter wrote:
>
> I'm very alive on what PMario is doing. It's very, very useful.
>
I did some development, but it won't be seen. .. I did use the TW
test-framework, to create automated tests. That's super boring but has to
be done,
