From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Renaming eglot -- or at least add an alias? Date: Thu, 06 Oct 2022 08:57:38 +0300 Message-ID: <834jwhsdd9.fsf@gnu.org> References: <83pmfdduix.fsf@gnu.org> <86wn9ji3ma.fsf@gmail.com> <86tu4lsnqk.fsf@gmail.com> <83ill0vzit.fsf@gnu.org> <835ygzv4p3.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24264"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Oct 06 08:02:31 2022 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 1ogJxm-00065v-Nh for ged-emacs-devel@m.gmane-mx.org; Thu, 06 Oct 2022 08:02:30 +0200 Original-Received: from localhost ([::1]:50640 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ogJxg-0001FI-MJ for ged-emacs-devel@m.gmane-mx.org; Thu, 06 Oct 2022 02:02:24 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37778) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ogJtQ-00073T-0c for emacs-devel@gnu.org; Thu, 06 Oct 2022 01:58:01 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:38114) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ogJtP-00082S-P0 for emacs-devel@gnu.org; Thu, 06 Oct 2022 01:57:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=rcTocREWUIlJPtBm6nOzGpR+BknNj/1Bt5+IUUpUwtE=; b=IUh+pklyyRxk tLfnBMJklaTxdGsU8QBUnHXNrh6DdQ08Rwb0vnRxPi8yol09yrxtd0/fkkDiZcD/JV/Cygxl62qtN Xg7jb7ub4DA/Khy/HQF0QoOCeir6GBxFZc+p7dcxSGHgD9HnLQPowRZ02z/Tm6cAPMhtXljVdKyM4 vNFwORxrucbiuQZOAsEnXHyXBkP6UFpun71G9Fd8/RRZ6bfSRJKXSCnfDR+5yy6f0rSNu27MzSxwb MDfrJjSQ81K6BM2Dl8kjXTlIXuNtKnZJVdtF5CCX9ZQNfd5/x4AYKkzJMim0del1jQBEXHjgq/wHD 4J+ObZkUKZWFTDiAVT50wQ==; Original-Received: from [87.69.77.57] (port=4296 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ogJt4-0006dM-RI; Thu, 06 Oct 2022 01:57:41 -0400 In-Reply-To: (message from Richard Stallman on Wed, 05 Oct 2022 17:35:26 -0400) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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:297057 Archived-At: > From: Richard Stallman > Cc: emacs-devel@gnu.org > Date: Wed, 05 Oct 2022 17:35:26 -0400 > > > Eglot doesn't parse code. It is a client of a protocol designed to > > allow applications to send requests about source code and receive > > results. The server which responds to the requests does parse the > > code, but Eglot doesn't. > > That's true, but it consists of implementation details. Users don't > need to know about them or think in those terms. For users, the > simple description of the package's job is to causes various Emacs > features to work by parsing code. I think from user's POV Eglot will be related to the features it enables. They won't care about code parsing that is the basis of that. > > But it's too early and premature to discuss what we will say in our > > menus, because we have no idea what these menus will be and which > > features they will activate. We should delay this discussion until > > after the merge, at which point we will be able to talk about concrete > > commands, variables, doc strings, and menu items. > > If users ask at some point to "use this package", it is important > what we call the package. The name must be Eglot, because that's how the package was called since 2017. We cannot possibly rewrite history or change people's memories. > How to deal with Eglot and Semantic is not clear to me. > > Is there any programming language which is supported both by Eglot and > by Semantic? Yes.