I've did this change, but it doesn't seem to work. Can somebody with more Lua knowledge take a look? See example here: User:Andrybak/sandbox/demonocat -- note, that page is added to Category:Wikipedians in Russia, but shouldn't be. — andrybak ( talk) 11:15, 29 August 2018 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please remove the line <noinclude>{{pp-template|small=yes}}</noinclude>
- protection templates are automatically handled by the documentation page. Thanks, --
DannyS712 (
talk)
06:39, 22 March 2019 (UTC)
Please incorporate a parameter to enable syntax highlighting of the preformatted text with <syntaxhighlight lang="{wikitext|html|etc.}">. I've attempted to develop this in the sandbox, without success. — swpb T • beyond • mutual 13:55, 11 May 2023 (UTC)
wikitext
is a good default that would work with HTML as well. BTW, do we even need html
as a parameter?
Jack who built the house (
talk)
08:40, 20 July 2023 (UTC)<pre>...</pre>
: you can't set display: inline
to <syntaxhighlight>...</syntaxhighlight>
, as suggested in
Template:Demo. Also, if used without <nowiki>...</nowiki>
, the templates are replaced with their code, but the code is still treated as code. Compare <big style="color:#DF0A24; font-size:1.4em;">✗</big> '''Fail'''
{{fail}}. This result is kind of better than with
<pre>...</pre>
: when there are no templates inside, <nowiki>...</nowiki>
can be omitted (but people might forget that they haven't used <nowiki>...</nowiki>
and use a template which will expand).
Jack who built the house (
talk)
19:52, 20 July 2023 (UTC)![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
I'm to make an edit to the module with several notable changes that you can see here or in the test cases:
*
, {|
) will work. It doesn't work for the first line now.|reverse=1
parameter to show the code snippet and the result in reverse order.<br>
after the code snippet by default, because it creates nonfunctional empty space. Many
usages of the template try to remove that space. I haven't witnessed cases where it was justified.|br=
will be renamed to |sep=
, from "separator" (|br=
will still work) because the more popular usage of the parameter is to add some meaningful text between the snippet and the result, not just line breaks.I've did this change, but it doesn't seem to work. Can somebody with more Lua knowledge take a look? See example here: User:Andrybak/sandbox/demonocat -- note, that page is added to Category:Wikipedians in Russia, but shouldn't be. — andrybak ( talk) 11:15, 29 August 2018 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please remove the line <noinclude>{{pp-template|small=yes}}</noinclude>
- protection templates are automatically handled by the documentation page. Thanks, --
DannyS712 (
talk)
06:39, 22 March 2019 (UTC)
Please incorporate a parameter to enable syntax highlighting of the preformatted text with <syntaxhighlight lang="{wikitext|html|etc.}">. I've attempted to develop this in the sandbox, without success. — swpb T • beyond • mutual 13:55, 11 May 2023 (UTC)
wikitext
is a good default that would work with HTML as well. BTW, do we even need html
as a parameter?
Jack who built the house (
talk)
08:40, 20 July 2023 (UTC)<pre>...</pre>
: you can't set display: inline
to <syntaxhighlight>...</syntaxhighlight>
, as suggested in
Template:Demo. Also, if used without <nowiki>...</nowiki>
, the templates are replaced with their code, but the code is still treated as code. Compare <big style="color:#DF0A24; font-size:1.4em;">✗</big> '''Fail'''
{{fail}}. This result is kind of better than with
<pre>...</pre>
: when there are no templates inside, <nowiki>...</nowiki>
can be omitted (but people might forget that they haven't used <nowiki>...</nowiki>
and use a template which will expand).
Jack who built the house (
talk)
19:52, 20 July 2023 (UTC)![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
I'm to make an edit to the module with several notable changes that you can see here or in the test cases:
*
, {|
) will work. It doesn't work for the first line now.|reverse=1
parameter to show the code snippet and the result in reverse order.<br>
after the code snippet by default, because it creates nonfunctional empty space. Many
usages of the template try to remove that space. I haven't witnessed cases where it was justified.|br=
will be renamed to |sep=
, from "separator" (|br=
will still work) because the more popular usage of the parameter is to add some meaningful text between the snippet and the result, not just line breaks.