This forum has a lot of coding related posts. Not everyone uses camelCase for all variable names, and if you have two snake_case variables anywhere in a post, the forum will by default automatically assume you want everything between them in italics. Even if the two are separated by multiple paragraphs. That makes absolutely NO sense on a forum like this. And while yes, code blocks certainly exist for longer pieces of code, I shouldn't need one every time I reference a variable name!

The same is true for pointers*

This really bugs me, it feels kinda like markdown syntax, only it's not and it does weird stuff. The markdown rules for * and _ seem to be fairly complex, presumably to deal with exactly this issue, including interactions with `inline code` (which be really nice if worked here).

_this is italics_. this_is_not. _this + is _not. _ this is not _

this * is italic * `this * is * not`

In many cases I just use notepad then copy/paste, as it seems the process for dealing with these style things is on typing, and not the overall text…, this also somehow messes up paragraph spacing but seems to be more reliable in general.

khawk said:
auto-markdown

If it is meant to be markdown, is it worth making a list of markdown things that don't work to fix? I was really under the impression it was only markdown inspired, as a lot of the syntax rules don't appear to apply (like leaving underscores alone with a character both sides, and not matching two “prefix” underscores).

For all the places the editor is used, presumably, same catches like going to do a little inline `std::tostring` and then oh no italics `std::unorderedmap`?

I'm not against it applying to pasted text either, and as such it could be useful, but only if is interpreted as expected as some quirks only seemed avoidable with pasting right now.

khawk said:
My personal complaint is the inability to use inline code. Since this is effectively CKEditor 5's autoformat feature, I'll need to go custom to fix some of these issues (of course, first checking if they're already fixed and just need an update).

Ah interesting, I actually reproduced a bunch of the things on their demo (which seems to have `inline code`) that caught me out, and found some issues on Github, but some years old.

Markdown autoformat italics bug
Autoformatting styles trigger within inline code

I also figured out some of the not-quite markdown things I thought just didn't work (e.g. I was trying <space>*<space>for a bullet point, which works on Google Docs / other places, and 4x indent for code). So just having a doc page stuck in front of me was useful in that regard.