Re: PL support

[João Távora]

On Sat, May 9, 2020 at 9:09 PM Dmitry Gutov <address@hidden> wrote:

> >> problem: everybody has to read every bug report and every commit message.
> > This is good.  I for one would like to spend a lot less time on Github.
> Maybe less happy later to see people complaining about some problems in
> Eglot on Twitter, Reddit, their blogs, etc.

I don't use those.  People know where to reach me.  If you frequent
those places, tell them I'm an email away. If they prefer to complain
in public in places I don't frequent, how is that my fault?

> > Really? Am I breaking backward compatibility all the time in Emacs?
> Not really. But that's the only conceptual advantage I could see:
> changing things in tandem. To *not* break things, at least for me,
> packages have to be considered separately... and then having them in the
> same repo is not so big an advantage.
>
> In any case, it's not my main demotivator. Increased debbugs and
> emacs-diffs traffic is. I'd rather much work on code that sorting
> through email not related to me. There is nothing at all personal in this.

Huh? Are you saying we make too many commits to Emacs?
Then make an email filter for emacs-diffs that checks the files touches,
surely you can do that. Same for debbugs.

> > Don't we have tests? Don't we have a (crude) namespacing system
> > for those libraries?  Don't we have Eli, the ever-vigilant? And Stefan
> > and everybody else?  And weren't you the one the one who told me
> > not to worry about that when refactoring Flymake?
>
> Eli who hasn't found time to try out Eglot yet. Same for Stefan, I imagine.

I thought you were concerned about protecting xref and eldoc and such.
so what has that got to do with it?

> Going back to xref and project.el, for instance, it wouldn't be
> sufficient to submit a patch and, in the explanation, assume my
> familiarity with Eglot's code.  So I kind of doubt it will help you a lot.

It wouldn't be indeed.  And it would not be necessary, either. This is
how it goes.  I tell you: "we need this interface in eglot.el, here is a
patch that opens it.  And you check it on its merits. And you get to
see it in action, and compiled in the same test run, even.". It's
really standard stuff.

? > https://lists.gnu.org/archive/html/emacs-devel/2017-08/msg00415.html
>
> Yup, it was a big rewrite, and Flymake was not used as much as e.g.
> Eldoc is. I'm not saying you can never break backward compatibility,
> just that you *usually* cannot break it.

But I _didn't_ break it, is what I'm saying (in fact flymake-proc.el
should still work as far as I can tell) I'm just pointing out you weren't
as concerned about it then, to the point of encouraging me not to
worry about it.

> > Really, are you telling me this?  Do you really think I (and other
> > developers) need
> > to be actively annoyed to be reminded of that? A file isn't enough 
> > separation?
> > That's not the point of GNU ELPA at all.
> Um, of course not. GNU ELPA is our repository of recommended packages.

Right, so you agree with me.  GNU ELPA It's not a way to "remind developers"
of the need for modularity.

Maybe you missed this: Eglot will always _also_ be in GNU ELPA.
And it has to be compatible with Emacs 26.3 so it cannot abuse new
interfaces.

João