You are not logged in.
I recently wanted to tell somebody to put their command output within [code] [/code] tags, and yikes - how amazingly difficult
The problem is that the tags will be interpreted, and I could find no intuitive way of escaping them - and I don't think [ code ] [ /code ] quite cuts it.
Eventually, I found a solution by thisoldman in an age-old thread.
I don't know if there is a better way to do it or not, but I'm fairly certain it would save some head-scratching if we were to add something about it in the BBCode info page
Offline
You put bbcode into code tags
[code][code]foo[/code][/code]
Offline
Or just link them to the bbc instructions. Why give them a fish when you can ... give them instructions on fishing.
And by using a link, you can kinda' demonstrate it too:
Please post your output in [code]...[/code] tags.
Note that other blocks would work too:
Please use [code]...[/code] tags, or [code]...[/code] tags.
(but please, for the love of god, don't actually use color tags like that as they make huge assumptions about everyone else's default color scheme.)
Last edited by Trilby (2023-02-16 17:00:52)
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Hehe, now it seems so easy, I don't know what I was doing.
I did try stuff like this: [em][code][/em]foo[em][/code][/em], which produces:
[/em]foo[em]
But I get it now; those codes must be attacked from the inside; not the outside
[[em]code[/em]]foo[[em]/code[/em]] does the trick: [code]foo[/code], puh - and thanks for all the fish
Offline
Eventually, I found a solution by thisoldman in an age-old thread.
That will only work for people who have a font installed that can display U+263. If that glyph is missing from the system a generic identifier box will be displayed instead of an invisible space.
Offline