- Could we have a page that clearly shows how to use code tags. With images. And possibly some other helpful info for new/long-time users.
- I.e. every time someone omits code tags, I could just link them to that page.
- Also, is there a way to literally write code tags, without them becoming code tags? In order to demonstrate how to use them.
- Any info from here could also be used (or rewritten, or with bits added/removed, or not used at all):
Tips for using the forum. - AutoHotkey Communityhttps://autohotkey.com/boards/viewtopic.php?f=3&t=29007

- HERE WE GO. Finally. Code. Tags.
AutoHotkey Community - BBCode guidehttps://autohotkey.com/boards/faq.php?mode=bbcode#f2r1
- Images on AHK can be fiddly. And anything on GitHub can be fiddly. So I'd be tempted to wait until I get my website back up and running, which could be a few months.
- I'm still interested in the write literal code tags question btw, anyone.
- Actually I sort of half-implied the question in this thread, that was posted just after mine:
Where is the "BBCode Guide"? - AutoHotkey Communityhttps://autohotkey.com/boards/viewtopic.php?f=3&t=42832
- As we're talking about long-term problems being resolved. And since it's relevant to tags. Why on the old forums did you get things like this '[*:2dlkkj93]', e.g. here, thanks.
Class definition syntax for AutoHotkey - Page 2 - Offtopic - AutoHotkey Communityhttps://autohotkey.com/board/topic/6547 ... key/page-2

- As we're talking about long-term problems being resolved. And since it's relevant to tags. Why on the old forums did you get things like this '[*:2dlkkj93]', e.g. here, thanks.
Class definition syntax for AutoHotkey - Page 2 - Offtopic - AutoHotkey Communityhttps://autohotkey.com/board/topic/6547 ... key/page-2

That is do to one or two or three forum conversions/overhauls that weren't well done, if I have it straight. tank would have more details if you want them.

- What is the docs tag.
- Re. 'Do as Helgef says'. It's OK to present tags with a space (something I've done before), but honestly, I think people need something even easier than that to get the message. Don't take chances with people understanding things.
- 'Disable BBCode'. Good call derz00. If you go to 'Full Editor & Preview', there is a 'Disable BBCode' option that you can untick.
- I would recommend that the BBCode guide also mention [ /c].
- I see things like '' in the old forum, which obviously isn't ideal, but with things like '[*:2dlkkj93]', what's odd is that the string is always different, it appears to be random.

- Thanks for sharing derz00. That's really good. However, I would warn that people will copy and paste that text, and wonder why it doesn't work!
- Similarly in Explorer, when you copy file datestamps from file property dialogs, it adds hidden characters in newer versions of Windows, which it didn't used to in the past. E.g. it does this on Windows 7.

forever ago, back on the ancient forums, back when I still used XP (with bblean shell) like 8 years ago, I attempted to combat this very issue by making a series of images.
The issue with things like this and making tutorials...
Those who need it won't find it. Those who don't need it will find it.
At that point it's just easier to tell them to use code tags than to fetch a link for them to hopefully read.

ofcourse that's not true for 100% of visitors, but it's a battle that cannot be won. Many just don't want to read or put much effort into anything.

Are there any (AHK) BBCode editors you can recommend (especially the indentation feature would be of interest)??

apart from the above images, I too made a series of sarcastic/tidbit-esque/over-the-top but still very helpful and detailed interactive flash slideshows ("tidtorials") using http://www.debugmode.com/wink/
but the same issue... Those who need it won't find it. Those who don't need it will find it.