Re: Warning message if clangd not found not displayed ?
"Christoph Cullmann (cullmann.io)" <[email protected]> Sun, 02 Oct 2022 18:22:20 +0200
| Newsgroups | gmane.comp.kde.devel.kwrite |
|---|---|
| Message-ID | <[email protected]> |
On 2022-10-02 17:01, Christoph Cullmann (cullmann.io) wrote: > On 2022-10-02 14:23, Alexander Neundorf wrote: >> On Mittwoch, 28. September 2022 00:39:07 CEST Alexander Neundorf >> wrote: >>> Hi, >>> >>> I digged a bit into my clangd problems, and got a little bit further. >>> If clangd is not installed (it doesn't crash anymore, I think it did >>> in >>> older versions, that's good :-) ), >>> In LSPClientServerManagerImpl::_findServer() it ends up in the branch >>> "we didn't find the server at all!", where a warning should be >>> displayed >>> using showMessage(), but I can't see the warning. "LSP Client" -> >>> "More >>> Options" -> "Show Messages" is checked. >>> Where should the message appear ? >> >> ok, I found it. The message that clangd could not be started is as a >> warning >> in the "Output" tab, which I usually never open. >> I really looked closely at kate to find the message, and I found it >> only after >> digging into the sources. I would assume that many users will not see >> it. >> >> IMO this warning message is so important that the user needs to see it >> (because it means that "Switch header" does not work, which at least >> to me is >> essential in navigating between files). >> I could change it from Warning to Error, then the tab will by default >> be >> opened if the message is issued. >> This may happen multiple times, e.g. also for each different language. >> I could add a flag so that it is issued only once as error for every >> language, >> and then as warning afterwards ? > > Hi, > > I think we downgraded this to warning as it was super annoying to have > always the > output tab there. > > On the other side, you now need to acknowledge the start the first > time, > too, perhaps a first time error would make sense, too. > > But the acknowledge is persistent, over application runs, I think the > same > must be true for errors, if we want that. > > But perhaps others have other ideas. Just had perhaps a better idea: I think it would in general make sense to highlight the output toolview button if new stuff arrives there. Perhaps even with the proper info/warning/error icon of the most urgent not yet seen thing. That would be imho non-intrusive and useful for other things, too. Greetings Christoph > > Greetings > Christoph > > >> >> Other ideas ? >> >> Thanks >> Alex -- Ignorance is bliss... https://cullmann.io | https://kate-editor.org