From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from fencepost.gnu.org (fencepost.gnu.org [IPv6:2001:470:142:3::e]) by sourceware.org (Postfix) with ESMTPS id 1F2F03858C41 for ; Wed, 17 May 2023 17:10:11 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 1F2F03858C41 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gnu.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gnu.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=v8t9oD5tYw1Ljg1/LL/ndeZm2Mn0jK8RazT4llRmfz0=; b=e1NGTE3GK0Erwxvb7GDB f8lZIByQW1N1HailAf1Knd6MzsgKyG9jAF8X3gp+mZWezP/89ynK1cxHnqNczqBb26DHnCc+ymue/ K8dWN+aEiZ3SKL4zAJHozHBVcNXjSzu3kDbqjMqjbQ7+i6WYoKkTl0Ls+Ycp5q56igCq3fY9EjfC5 YSPnH0Nlv7Ww5zmMQBwvoFmGhKV0dYiY7WHPNWSq254ltTPh+zcVS0jR72qllzWGgGLvrC//FnQh/ +zI7X8XN9SRUCNgAlHKsqjbkluiBGCL6yMSnjMuf+kVvxyNDvhcUuN4MBgwTDKZYy0Yhsr0vrpItZ YbP8LmTy76SBGA==; Received: from [87.69.77.57] (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 1pzKfA-0004ki-Sr; Wed, 17 May 2023 13:10:10 -0400 Date: Wed, 17 May 2023 20:10:18 +0300 Message-Id: <83353uyjd1.fsf@gnu.org> From: Eli Zaretskii To: David Malcolm Cc: gcc@gcc.gnu.org, fche@elastic.org In-Reply-To: (message from David Malcolm on Wed, 17 May 2023 11:46:58 -0400) Subject: Re: LSP based on GCC References: <83a5y3xcai.fsf@gnu.org> MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=2.3 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_SHORT,RCVD_IN_BARRACUDACENTRAL,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: > From: David Malcolm > Cc: "Frank Ch. Eigler" > Date: Wed, 17 May 2023 11:46:58 -0400 > > > Emacs 29, to be released soon, will come with a built-in client for > > the LSP protocol.  This allows to enhance important Emacs features, > > such as at-point documentation, on-the-fly diagnostic annotations, > > finding definitions and uses of program identifiers, enhanced > > completion of symbols and code, etc., based on capabilities of LSP > > servers. > > Excellent. Do you have a handy link to the specific LSP methods that > Emacs consumes? IIUC what you mean (I'm not an expert on LSP), then you will find the answers here: https://git.savannah.gnu.org/cgit/emacs.git/tree/lisp/progmodes/eglot.el#n775 https://git.savannah.gnu.org/cgit/emacs.git/tree/lisp/progmodes/eglot.el#n1721 > >   https://gcc.gnu.org/legacy-ml/gcc-patches/2017-07/msg01448.html > > > > which described the initial implementation of LSP in GCC, but I seem > > to be unable to find out what happened with that since then. > > > > Are there plans for implementing the LSP in GCC?  If so, which GCC > > version is expected to have this included? > > I wrote that prototype, but I haven't touched it since 2017, and I > already have more than enough other work, alas. I'm happy to help if > someone wants to pick up the work and finish it. I hope someone will, thanks. > BTW, in GCC 13 I implemented SARIF support for capturing diagnostics in > a standardized JSON-based format [2]; see e.g. the "Diagnostic > Serialization" slides in [3] which shows VS Code showing GCC > diagnostics with squiggly underlines. Has anyone implemented SARIF > support for Emacs yet? AFAIK, not yet. I'll ask on the Emacs devel list if anyone is interested.