Skip to content
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

disable diagnostics panel #2179

Merged
merged 1 commit into from
Jan 28, 2023
Merged

disable diagnostics panel #2179

merged 1 commit into from
Jan 28, 2023

Conversation

glaucocustodio
Copy link
Contributor

@rchl
Copy link
Member

rchl commented Jan 27, 2023

There are also those places that have a default of 2:

"default": 2,

r("show_diagnostics_panel_on_save", 2)

BTW. I've suggested this change so obviously I'm fine with it. :)
I believe others have also suggested that before (@jwortmann ?).

@jwortmann
Copy link
Member

I believe others have also suggested that before (@jwortmann ?).

Yes, I always thought that this default value is annoying :D
Another related setting, where I would change the default value is "diagnostics_panel_include_severity_level" (I would use 3 instead of 4, because iirc* diagnostics with the "hint" severity are not supposed to be shown in the UI - we also draw the stippled underline in the view though)

* I think that I've read this somewhere in an issue from the LSP specs repository, but I don't know the exact place right now.

@glaucocustodio
Copy link
Contributor Author

just did the changes

@jwortmann
Copy link
Member

Please note that changing "diagnostics_panel_include_severity_level" was just a suggestion from my side and perhaps needs a separate discussion first.

I already removed the gutter icon for the "hint" severity in a previous PR #2086 (this also contains a link to the related discussion/clarification about the idea behind the "hint" severity rendering).

In VSCode, diagnostics with this severity are not shown in the "Problems" panel, by the way.

@glaucocustodio
Copy link
Contributor Author

ok, just reverted diagnostics_panel_include_severity_level changes

@rchl
Copy link
Member

rchl commented Jan 27, 2023

Yeah, probably best to have it as a separate PR if we'd want that (to be honest I wouldn't mind but would be good to hear opinions of other maintainers).

@rchl rchl merged commit dde4a66 into sublimelsp:main Jan 28, 2023
rchl added a commit that referenced this pull request Jan 31, 2023
* main: (80 commits)
  Perform inlay hint action on double instead of single click (#2175)
  support canceling pending completions request (#2177)
  Implement type hierarchy request (#2180)
  fix stale state or lack of updates on changing branches (#2182)
  Add timestamp and request duration in LSP logs (#2181)
  don't show diagnostics panel on save by default (#2179)
  trigger "on_server_response_async" also for "initialize" response (#2172)
  feat(API): allow setting additional text in permanent server status (#2173)
  Implement call hierarchy request (#2151)
  workaround for View Listeners not being attached for new transient view (#2174)
  Make Document Symbols behavior more consistent with built-in Goto Symbol (#2166)
  docs: fsautocomplete config - remove redundant argument (#2165)
  Allow missing window/workDoneProgress/create request from the server (#2159)
  Use "plaintext" language ID for plain text files (#2164)
  Improve type annotations (#2162)
  Don't use "escapeall" extension when formatting with mdpopups (#2163)
  Cut 1.21.0
  Fix inlay hint parts wrapping into multiple lines (#2153)
  Ensure commands triggered from minihtml run on correct view (#2154)
  Add "Source Action" entry to the "Edit" main menu (#2149)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants