|
From: | Dmitry Gutov |
Subject: | Re: My perspective as a mid-level user on pros/cons of different editors |
Date: | Wed, 20 May 2020 17:13:21 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 |
On 20.05.2020 17:06, João Távora wrote:
The lack of a binging to show the doc (last time I tried) kind of hurts.There is C-h ., which you yourself suggested once. But interesting that you bring that up. I did put one now, precisely because it kind of hurts, and because C-h . should be handled by eldoc.el or whereabouts.
'C-h .' shows documentation for a function? Or diagnostics/errors?
IIUC, LSP also provides extra actions that tie into refactoring, reorganizing imports, etc. How does Eglot deal with it?In LSP, they are associated with the diagnostic object. So they go into flymake's facility of interactive diagnostics. But part of it is currently in Eglot, as commands. The long-term goal is for it not to be, as I stated.
No diagnostics will ask you to refactor a method. To do a rename/extract/override kind of action.
That's simply a missing feature, I guess.
reduce it to `eglot-connect` and `eglot-disconnect`, maybe call them `start-ide-ing` and `stop-ide-ing` for abstraction.That sounds pointless. It's not like the users will look for 'M-x start-ide-ing' command specifically.Why? Just tell them at the splash screen: "to start advanced IDE features, M-x start-ide-ing". Weren't you the one talking about a "how to IDE" tutorial? Or was it someone else. It sould be a 1-step tutorial in this case.
Um, okay. If there is a splash screen, couldn't it say 'M-x eglot-start'? Or do you dislike that name now, for some reason?
[Prev in Thread] | Current Thread | [Next in Thread] |