# Disable linting doesn't work

**URL:** <https://discourse.julialang.org/t/disable-linting-doesnt-work/29376>\
**Category:** VS Code\
**Created:** [October 1, 2019, 6:26pm UTC](https://discourse.julialang.org/t/disable-linting-doesnt-work/29376 "2019-10-01T18:26:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![raff](https://avatars.discourse-cdn.com/v4/letter/r/5e9695/32.png) [@raff](https://discourse.julialang.org/u/raff)\
**Post date:** [October 1, 2019, 6:26pm UTC](https://discourse.julialang.org/t/disable-linting-doesnt-work/29376/1 "2019-10-01T18:26:59Z")

</div>

I tried to uncheck the `Run Linter` option in the settings, but VSCode still run the linter (many yellow curly underscore on my perfectly working code).

I use domain specific lang using macros a lot in my code where linter cannot detect. How to turn it off?

---

<div class="post-metadata">

**Author:** ![ufechner7](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ufechner7/32/51363_2.png) [@ufechner7](https://discourse.julialang.org/u/ufechner7)\
**Post date:** [October 2, 2019, 12:09pm UTC](https://discourse.julialang.org/t/disable-linting-doesnt-work/29376/2 "2019-10-02T12:09:10Z")

</div>

Perhaps it is this bug?  
[https://github.com/julia-vscode/julia-vscode/issues/813](https://github.com/julia-vscode/julia-vscode/issues/813)

---

<div class="post-metadata">

**Author:** ![jasonsun0310](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jasonsun0310/32/10082_2.png) [@jasonsun0310](https://discourse.julialang.org/u/jasonsun0310)\
**Post date:** [October 8, 2019, 6:15pm UTC](https://discourse.julialang.org/t/disable-linting-doesnt-work/29376/3 "2019-10-08T18:15:06Z")

</div>

I agree. It is very annoying… I am accustomed to write code without any checker… And I have to use vscode for access to remote Julia REPL. It annoys the hell out of me that they make is impossible to disable the linter… If the linter is not mature enough to be shipped, then don’t. Leave it optional. Who would like to see 2k+ warnings in a perfectly designed code!!!