From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: =?UTF-8?B?Sm/Do28gVMOhdm9yYQ==?= Newsgroups: gmane.emacs.devel Subject: Re: Drop the Copyright Assignment requirement for Emacs Date: Sun, 10 May 2020 15:08:20 +0100 Message-ID: References: <9mmFgzvrBwjt_n_VJyaJdXINraNi5HsGpwq-0MLeKiJA7kG2BQA4uywrzjyz7lpRS0OZDpjEi8lspOKYUA7P_QsODsDew_8nbH960G55fmY=@protonmail.com> <878silajdl.fsf@ericabrahamsen.net> <87tv18pyh4.fsf@russet.org.uk> <83zhaih0oz.fsf@gnu.org> <83pnbegsvm.fsf@gnu.org> <83imh5hby1.fsf@gnu.org> <2e4e8ce9-d857-f3e3-31cf-a40dee67bd25@yandex.ru> <442916f9-71f6-5daf-efbf-790685765efe@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="74383"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , Stefan Monnier , emacs-devel To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun May 10 16:09:23 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jXmdv-000JG2-Au for ged-emacs-devel@m.gmane-mx.org; Sun, 10 May 2020 16:09:23 +0200 Original-Received: from localhost ([::1]:58318 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jXmdt-00068w-UX for ged-emacs-devel@m.gmane-mx.org; Sun, 10 May 2020 10:09:21 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43670) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jXmd9-0005CD-09 for emacs-devel@gnu.org; Sun, 10 May 2020 10:08:35 -0400 Original-Received: from mail-io1-xd2d.google.com ([2607:f8b0:4864:20::d2d]:33339) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jXmd7-0000af-V7; Sun, 10 May 2020 10:08:34 -0400 Original-Received: by mail-io1-xd2d.google.com with SMTP id k18so6775319ion.0; Sun, 10 May 2020 07:08:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=J8d74EUOyCnf4YOYtyGfP7DBm6SLkpxBjQybiRfZmIc=; b=XMKGmaCdEza70/agQnTZB1yq4hEEQ6bG8EHwHj5sWOuT9dBGAt4JnA7dXJOqNQDIhw 1BiyQQYwlWP/f7QcMPP4I+VK5Q+UfxYrrb42EQjTCBPXEDbNcUKVDOwzU4cvi8es4xxi vVRp4I99qE2wKmLPlXKlAsrbmVOn3IFxJrBk0WarafsxURd31Y20sHDFr5oB7IEStqpF Y4i0kTcV9EmxmTYgKihUgbti08okro3idlDVQbJ/ISuBebMFy6mdfQLxgcqoCrUCKag8 DIb4K1BSqJYdsla6kD+g4zFNlu+CEnmM56rDLR5kzl4u5fq8HiWy0sRHmZrZyv081p0Y Wdxg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=J8d74EUOyCnf4YOYtyGfP7DBm6SLkpxBjQybiRfZmIc=; b=qJ/irJL9M+pZ91ZcLhDVfZLfnZM1PrVmtCnwtJ/6IO9WOtVGe/IVnpYeIsmJLbjdo9 MKVS5c8+O9sfHfJG89zyt6stOJRre7ybzEDGDxeRyK5LTqVJnESRI6Ubzlh9RR3Fef2U 11EcGNs7/DpHpz1KGlHjWtpoFYgjQYaWYJ3l2RyX9YaTcSzVwUlKr3dVb45qUp6Tojyc xJgx2H6wgbAu5ZozKEoBhlw4XcVnwQehLj0QPfqbplhl5/5qiZzZ1AXuKDbz7Ihs2rLx 1zmWvvci8BcrzyyTWZlpcaRCVt1rZIlghGF68TTXUkNSlFA5gjbYprVXxBMUiClVWs/W j3qA== X-Gm-Message-State: AGi0Pub/JDMpJIe9iNJofdcOg7RQsFwIAd4tmWix6Bt033yypUJ1K2Wr uMThK5otFPdL44jb23RTBKa/L+2LVbx5zCF4VYk= X-Google-Smtp-Source: APiQypIighff9QNgVgDfGknSInmnlnEstYufL2fH9aksF3N0lnwFO2RDfa5w7XnuwB1z6LuDo4kcMeckyC/zTRzSMlc= X-Received: by 2002:a6b:6a13:: with SMTP id x19mr11073783iog.175.1589119712619; Sun, 10 May 2020 07:08:32 -0700 (PDT) In-Reply-To: <442916f9-71f6-5daf-efbf-790685765efe@yandex.ru> Received-SPF: pass client-ip=2607:f8b0:4864:20::d2d; envelope-from=joaotavora@gmail.com; helo=mail-io1-xd2d.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -10 X-Spam_score: -1.1 X-Spam_bar: - X-Spam_report: (-1.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FROM_EXCESS_BASE64=0.979, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:249658 Archived-At: On Sun, May 10, 2020 at 2:12 PM Dmitry Gutov wrote: > On 09.05.2020 18:52, Jo=C3=A3o T=C3=A1vora wrote: > > >> I'm not sure for what purposes, but hooks are flexible enough for this > >> to be possible today already (without Eglot in the core). > > Yes, that works. But Eglot doesn't have only these kinds of interfaces= . It > > also has generic functions. I guess we could have just a "lsp-interfac= e.el" > > in the core that defines the generic functions and no implementations. > I suppose so. Though I'd like to look at its contents. So far I don't > have any solid idea what this file would contain. I think it's important to clarify something. I'm not "selling" you lsp-interface.el in exchange for "Eglot in the core". I'm just stating that if you're worri= ed about protecting the hypothetical, however unlikely, entrance of another LSP client into Emacs, such a file can be developed from parts of Eglot. In fact, I think it's a good idea to do so regardless of the possibility th= at other LSP clients make it into the core. And for sure you'll be able to participate in its design. But that goal isn't in any way mutually exclusi= ve with Eglot being in the core. Quite the contrary: it is facilitated by it. In fact that's exactly what I did with jsonrpc.el (which lsp-mode.el never took up) It was hard enough doing the two-repository dance then, and I don't want to do that again. So unless you state a negative, irrefutable, irreparable consequence of having eglot.el developed in emacs.git instead of some other place, I'll bring the issue to a discussion with the Eglot developers, a group which you aren't (yet) a member of, but whom I think are the main ones to consult regarding this this, since Eli and Stefan haven't stated any objections with such a move. Jo=C3=A3o