Seb Tomasini
Seb Tomasini
Thanks, didn't think to try that. Perhaps `postgresql:` should be added for consistency. I'm left wondering whether the issue is with the docset or zeal itself?
This is still an issue at vscode 1.53.2, and the above dependent issues are closed. Is a fix in the pipeline?
As a temporary workaround, pull the `css_completions.py` out of your `Packages\CSS.sublime-package' and modify line 449 (build 3143, may vary on newer builds) to: ``` css_selector_scope = "source.css - meta.selector.css, source.scss...
There are positive use-cases for a number of the above suggestions. I propose: `@ts-ignore` as present behaviour `@ts-ignore TSxxx [TSxxx ...]` suppress specific error(s) `@ts-ignore-start` start block to ignore `@ts-ignore-start...
=== stil looks imbalanced at a number of font sizes from 22 down.
@philippnurullin I'd like this option too, but I can't see how in sublime text. ST 3.2 supports some `ssXX` stylistic sets (where `XX`
@sewkokot Agree with all your points. FWIW I created a separate issue #104 about dotted 0 being off-center at different font sizes.
@philippnurullin Hey, no apology necessary :slightly_smiling_face: I agree that having multiple fonts for different tastes could easily get out of hand and I also like how Input Mono has solved...
If you zoom up the above image a bit, you can see that the 'a' part is off-center, too low at 8 and too high at 10.
Experiencing similar delays when attempting to autocomplete (tab) or raise intellisense popup (ctrl+space) for object member. For example: ```ts let x = {a: 'test', b: 'test'} x. // [ctrl+space] here...