-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Never option on tab warning isn't "sticky" #203
Comments
Stale because you haven't looked at it? |
@stretch327 indeed ! We are mostly 2 persons ( @stevenh and myself ) to maintain vscode-groovy-lint for free, and our available time is limited... sometimes it can take time :/ Maybe you'd like to help by submitting a pull request with a fix ? |
Never is currently acting as no for this session vs never ask me again, what's the intended behaviour here? |
@stevenh "Never again for any Groovy file i'll open with this vscode" ^^ I don't know if it's good or not, but it was the previous behaviour so people are probably used to it ^^ |
Thanks for the confirmation. I can confirm it's only set in a session variable there is no configuration option I could find for that, let me know if I missed something @nvuillam . If the above is correct, to fix we would need to introduce a config option for this and have the dialog option interact with that and the document handler subscribe to config updates, so a little bit involved. |
@stevenh let's check how it was done before your refactoring :) |
Sounds like you guys have ideas how to fix it. Please keep this case open! |
When you first open a groovy file and get the warning that says:
"CodeNarc linter doesn't like tabs, let's replace them by spaces ?"
The options that are available are "Always, Yes, No and Never"
If you select Never, it is treated as if you clicked "No" and you still have to answer this question again each time you open a new document.
The text was updated successfully, but these errors were encountered: