Re: My perspective as a mid-level user on pros/cons of different editors

[João Távora]

On Wed, May 20, 2020 at 2:59 PM Dmitry Gutov <address@hidden> wrote:
>
> On 20.05.2020 16:32, João Távora wrote:
> > Anyway, it is precisely in this sense that I try that Eglot
> > provide the least amount of interactive commands and
> > user options, and no keybindings at all.  So that people
> > "see it" as little as possible of it.
>
> 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.

And that is why I made eldoc.el a :core package ;-)

Anyway, see https://github.com/joaotavora/eglot/issues/454

> > They just see xref, project,
> > flymake diagnostics, eldoc, etc. This is quite different
> > from lsp-mode (at least the last time I looked at it).
>
> 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.

> > 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.

João