And until suppressed parsing is invented, I just wanted to add that does
not have to be escaped if is escaped.
So only lt;some text is enough :-)
On Sunday, February 8, 2015 at 9:19:43 PM UTC+2, sini-Kit wrote:
lt; and gt;
среда, 4 февраля 2015 г., 17:31:15 UTC+3 пользователь
OK, in your case, I'm not :-)
On Monday, February 9, 2015 at 2:11:18 PM UTC+2, Stephan Hradek wrote:
Am Montag, 9. Februar 2015 12:18:28 UTC+1 schrieb Branimir Braykov:
And until suppressed parsing is invented, I just wanted to add that
does not have to be escaped if is escaped.
So
Am Montag, 9. Februar 2015 12:18:28 UTC+1 schrieb Branimir Braykov:
And until suppressed parsing is invented, I just wanted to add that does
not have to be escaped if is escaped.
So only lt;some text is enough :-)
Are you sure?
\define showme(txt) $txt$
# showme testgt;gt; - correct
#
lt; and gt;
среда, 4 февраля 2015 г., 17:31:15 UTC+3 пользователь Branimir Braykov
написал:
Hi, All,
and are not actually wiki characters, but whenever I want to write
text like this: some of my text I get some text rendered.
Is this a bug? If its not, then I cannot find anything
And I guess it is a fair assumption that there is no generic way to
'escape' any character that might otherwise be interpreted by the parser?
i.e. I ran into a problem recently where I really needed to have two
forward slashes next to each other in some text (//). However I could
never get
Hi Bob
I would think it would be useful if there were *some* mechanism that
could mean interpret the next character exactly.
I agree. One option that's been discussed in the past is check for a
preceding ~ before every parse rule, and suppress it if it is found. I
think it may be more flexible
One option to disable italic rendering is with the \rules pragma.
eg: If you include this into a tiddler the // will not be rendered.
\rules except italic
-mario
--
You received this message because you are subscribed to the Google Groups
TiddlyWiki group.
To unsubscribe from this group
Please, don't suggest to use html entities. I know about it, but I want to
find a general solution.
If you prefer a general solution instead of the entities lt; gt;, you
can use #60; and #62;
Is there actually a d difference about numbered or textual entities?
To me, both are equally
Am Mittwoch, 4. Februar 2015 17:51:55 UTC+1 schrieb Tobias Beer:
Please, don't suggest to use html entities. I know about it, but I want to
find a general solution.
If you prefer a general solution instead of the entities lt; gt;, you
can use #60; and #62;
Is there actually a d
On Wednesday, February 4, 2015 at 7:14:37 AM UTC-8, Branimir Braykov wrote:
10x,
what I didn't think of is exactly that this is html and treated for html
tags.
The solution that is best for me is using the space after it.
However, it is still strange, because in TWC this works as it is.
10x,
what I didn't think of is exactly that this is html and treated for html
tags.
The solution that is best for me is using the space after it.
However, it is still strange, because in TWC this works as it is.
On Wednesday, February 4, 2015 at 5:02:24 PM UTC+2, Jed Carty wrote:
and are
Am Mittwoch, 4. Februar 2015 15:31:15 UTC+1 schrieb Branimir Braykov:
P.S.
Please, don't suggest to use html entities. I know about it, but I want to
find a general solution.
If you prefer a general solution instead of the rntities lt; gt;, you can
use #60; and #62;
--
You received
12 matches
Mail list logo
