Clément Sipieter [6π]

@zyrikby @lrfuentesw we should check that there is no side effect and set this configuration as default.

related PR #132

I'm using vscode 1.51 and I don't have any issue… ``` Version: 1.51.1 Commit: e5a624b788d92b8d34d1392e4c4d9789406efe8f Date: 2020-11-10T23:31:29.624Z Electron: 9.3.3 Chrome: 83.0.4103.122 Node.js: 12.14.1 V8: 8.3.110.13-electron.0 OS: Linux x64 5.3.0-64-generic ```...

I reproduced this bug.

As usual, I'm pretty busy but I will look this week-end to give you what I've done in this way. For example, for PDF export, I trigger the following command...

in the same vein: this following cases should be displayed bold (I took Emacs and Latex Export as reference) ``` (*test*) {*test*} "*test*" '*test*' ... ? ``` But these should...

encore un cas :) ``` *bold* *not bold* *bold* *not bold* ```

except for the last case, the following regex seems to work (example with * for bold): ``(^|[\\s\\(\\{\"'])\\*(\\S|\\S.*?\\S)\\*($|[\\s\\)\\}\"'])``

There is also an overflow to neighboring characters when underline `` _underline_ ``, surrounding space are also underline. By adding ``( { ' " `` as other possible characters before...

_last edited: 2018-08-10_ Hi, I suggest the following validation org file: ``` org #+OPTIONS: ^:nil #disable super/sub script. * match bold, italic, code, verbatim, strike-through but NOT UNDERLINE !!! /Is...