-
Notifications
You must be signed in to change notification settings - Fork 31
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
[infoview] Show notices on panel instead of diagnostics #125
Closed
ejgallego opened this issue
Dec 27, 2022
· 0 comments
· Fixed by #128 or ocaml/opam-repository#22861
Closed
[infoview] Show notices on panel instead of diagnostics #125
ejgallego opened this issue
Dec 27, 2022
· 0 comments
· Fixed by #128 or ocaml/opam-repository#22861
Labels
kind: enhancement
New feature or request
part: client (VSCode)
part: goals and info panel
part: lsp server
part: protocol (LSP)
Milestone
Comments
ejgallego
added
kind: enhancement
New feature or request
part: client (VSCode)
part: lsp server
part: protocol (LSP)
part: goals and info panel
labels
Dec 27, 2022
ejgallego
added a commit
that referenced
this issue
Dec 27, 2022
This seems more sensible as Coq (legacy) will produce large amounts of these kind of Coq messages when for example `Search` or `About` is used. Thus, users can click on the concrete command and obtain the messages information in the side panel; moreover, this allows for better rendering opportunities. A configuration option allows to restore old behavior. Fixes #125
ejgallego
added a commit
that referenced
this issue
Dec 27, 2022
This seems more sensible as Coq (legacy) will produce large amounts of these kind of Coq messages when for example `Search` or `About` is used. Thus, users can click on the concrete command and obtain the messages information in the side panel; moreover, this allows for better rendering opportunities. A configuration option allows to restore old behavior. Fixes #125
ejgallego
added a commit
that referenced
this issue
Dec 27, 2022
This seems more sensible as Coq (legacy) will produce large amounts of these kind of Coq messages when for example `Search` or `About` is used. Thus, users can click on the concrete command and obtain the messages information in the side panel; moreover, this allows for better rendering opportunities. A configuration option allows to restore old behavior. Fixes #125
ejgallego
added a commit
that referenced
this issue
Dec 27, 2022
This seems more sensible as Coq (legacy) will produce large amounts of these kind of Coq messages when for example `Search` or `About` is used. Thus, users can click on the concrete command and obtain the messages information in the side panel; moreover, this allows for better rendering opportunities. A configuration option allows to restore old behavior. Fixes #125
ejgallego
added a commit
that referenced
this issue
Jan 3, 2023
This seems more sensible as Coq (legacy) will produce large amounts of these kind of Coq messages when for example `Search` or `About` is used. Thus, users can click on the concrete command and obtain the messages information in the side panel; moreover, this allows for better rendering opportunities. A configuration option allows to restore old behavior. Fixes #125
ejgallego
added a commit
that referenced
this issue
Jan 3, 2023
This seems more sensible as Coq (legacy) will produce large amounts of these kind of Coq messages when for example `Search` or `About` is used. Thus, users can click on the concrete command and obtain the messages information in the side panel; moreover, this allows for better rendering opportunities. A configuration option allows to restore old behavior. Fixes #125
ejgallego
added a commit
that referenced
this issue
Jan 3, 2023
This seems more sensible as Coq (legacy) will produce large amounts of these kind of Coq messages when for example `Search` or `About` is used. Thus, users can click on the concrete command and obtain the messages information in the side panel; moreover, this allows for better rendering opportunities. A configuration option allows to restore old behavior. Fixes #125
ejgallego
added a commit
that referenced
this issue
Jan 3, 2023
This seems more sensible as Coq (legacy) will produce large amounts of these kind of Coq messages when for example `Search` or `About` is used. Thus, users can click on the concrete command and obtain the messages information in the side panel; moreover, this allows for better rendering opportunities. A configuration option allows to restore old behavior. Fixes #125
ejgallego
added a commit
that referenced
this issue
Jan 3, 2023
This seems more sensible as Coq (legacy) will produce large amounts of these kind of Coq messages when for example `Search` or `About` is used. Thus, users can click on the concrete command and obtain the messages information in the side panel; moreover, this allows for better rendering opportunities. A configuration option allows to restore old behavior. Fixes #125
ejgallego
added a commit
that referenced
this issue
Jan 4, 2023
This seems more sensible as Coq (legacy) will produce large amounts of these kind of Coq messages when for example `Search` or `About` is used. Thus, users can click on the concrete command and obtain the messages information in the side panel; moreover, this allows for better rendering opportunities. A configuration option allows to restore old behavior. Fixes #125
ejgallego
added a commit
that referenced
this issue
Jan 4, 2023
This seems more sensible as Coq (legacy) will produce large amounts of these kind of Coq messages when for example `Search` or `About` is used. Thus, users can click on the concrete command and obtain the messages information in the side panel; moreover, this allows for better rendering opportunities. We also implement a detailed display for errors, as Coq errors can be large and don't fit properly in the diagnostics list. A configuration option allows to restore old behavior. Fixes #125
ejgallego
added a commit
to ejgallego/opam-repository
that referenced
this issue
Jan 6, 2023
CHANGES: ------------------------ - Send an error to the client if the client and server versions don't match (@ejgallego, ejgallego/coq-lsp#126) - Parse options -noinit, -indices-matter, and -impredicative-set from `_CoqProject` (@artagnon, @ejgallego, ejgallego/coq-lsp#140, ejgallego/coq-lsp#150) - Log file `log-lsp.txt` has been removed in favor of `coq-lsp.trace.server` (@artagnon, @ejgallego, ejgallego/coq-lsp#130, ejgallego/coq-lsp#148) - Added --bt flag to print a backtrace on error (@Alizter, ejgallego/coq-lsp#147) - A detailed view of Coq errors is now displayed in the info panel (@ejgallego, ejgallego/coq-lsp#128) - Coq "Notice" messages, such as the ones generated by `About` or `Search` are not shown anymore as diagnostics. Instead, they will be shown on the side panel when clicking on the corresponding command. The `show_notices_as_diagnostics` option allows to restore old behavior (@ejgallego, ejgallego/coq-lsp#128, fixes ejgallego/coq-lsp#125) - Print some more info about Coq workspace configuration (@ejgallego, ejgallego/coq-lsp#151) - Admit failed `Qed` by default; allow users to configure it (@ejgallego, ejgallego/coq-lsp#118, fixes ejgallego/coq-lsp#90)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind: enhancement
New feature or request
part: client (VSCode)
part: goals and info panel
part: lsp server
part: protocol (LSP)
As of today, we show Coq's feedback
Notice
using diagnostics. This includesSearch
,Check
, etc...This is not good in most cases, instead, make that optional, and show them instead as messages in the goal / info panel.
The text was updated successfully, but these errors were encountered: