just a bug, will come back
Hi!
How to prevent this type of transformation?
Not every time I want to see ≠ instead of !=.
That’s a pity.
There needs to be a way to disable this entirely. For me at least, and probably for many users who work with code, this feature is always unwanted.
To prevent this, I use code blocks and inline code blocks, but the inline code blocks are annoying because they are created only after the “smart” typing triggers. Still, after a bit of fiddling, it works. Forcing programmers to use inline code blocks might even be the correct approach (provided the inline code blocks behaved better). For most people, the “smart” typing is what they want, I believe. And disabling this feature entirely is probably something one does not want, either.
For those who want it, we’re implementing the ability to do so.
