lonix1

@JoeShook That's quite smart. But when logging to console (and thus indirectly to file via bash redirection), it's human readable - don't you lose the structured logging?

@JoeShook If I remember correctly, the console logger doesn't do structured logging. So although it's an excellent workaround, there is a tradeoff - native log rotation vs structured logging. Thanks...

@adamsitnik That is an interesting problem. Maybe it could be solved with a new option, e.g. `FileMode.AtomicAppend`. Also, I am now confused :) ... are you saying this feature in...

@KaNaHaKEsUh That isn't a fix - it assumes you want to use flatpak. The problem is with apt.

@KaNaHaKEsUh Your original comment, before you changed it, said "FIX", not "workaround". I don't recall insulting you. Your rude behavior says it all.

The same problem exists in c#: ````cs /// /// shown normally /// // incorrectly shown as struck /// ````

You're right - it would be good not to redo the work vscode already does, and handle only bad chars that vscode doesn't catch. But how would we even know...

@TheSench Thank you for the detailed overview. In fact in might be a good idea to add that list to the docs, because I'm sure many users will wonder about...

I agree it would be nice to have a config option to completely disable those snippets / intellisense.