From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.bugs Subject: bug#50244: 28.0.50; Support project-wide diagnostics reports in flymake.el Date: Mon, 30 Aug 2021 02:27:52 +0300 Message-ID: <8dfca367-baa8-c4ae-8e6b-8ca41d5a63d6@yandex.ru> References: <87bl5hm5qj.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27741"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 To: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= , 50244@debbugs.gnu.org, theo@thornhill.no, p.stephani2@gmail.com Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Aug 30 01:28:46 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1mKUEH-00073N-CW for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 30 Aug 2021 01:28:45 +0200 Original-Received: from localhost ([::1]:34862 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mKUEG-0001Xt-Ch for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 29 Aug 2021 19:28:44 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55620) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mKUDb-0000Sb-7S for bug-gnu-emacs@gnu.org; Sun, 29 Aug 2021 19:28:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:46192) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mKUDa-000862-IF for bug-gnu-emacs@gnu.org; Sun, 29 Aug 2021 19:28:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mKUDa-0002xL-8k for bug-gnu-emacs@gnu.org; Sun, 29 Aug 2021 19:28:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Dmitry Gutov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 29 Aug 2021 23:28:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 50244 X-GNU-PR-Package: emacs Original-Received: via spool by 50244-submit@debbugs.gnu.org id=B50244.163027968111356 (code B ref 50244); Sun, 29 Aug 2021 23:28:02 +0000 Original-Received: (at 50244) by debbugs.gnu.org; 29 Aug 2021 23:28:01 +0000 Original-Received: from localhost ([127.0.0.1]:57738 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mKUDZ-0002x6-Da for submit@debbugs.gnu.org; Sun, 29 Aug 2021 19:28:01 -0400 Original-Received: from mail-wm1-f51.google.com ([209.85.128.51]:52045) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mKUDY-0002wq-CM for 50244@debbugs.gnu.org; Sun, 29 Aug 2021 19:28:00 -0400 Original-Received: by mail-wm1-f51.google.com with SMTP id u15so7651810wmj.1 for <50244@debbugs.gnu.org>; Sun, 29 Aug 2021 16:28:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=rAmbFyk5T+IIgPkQW2TdYk1o+379sHiKmwL7dbbh6IM=; b=EHUbK8Ben8h1RUyPEA9sSGw+kawFoXxrriQMTjbnC1F34f2ayDEXVAiy9IU8oQyyz+ YgnOu7tfdG9+ewnWV43UjE45mVQAxFNQwLAXEN2SZ0L/Vz4MeHrG7MZgeQHdEG6q6s/d 7dnBD0ryPoP/rhQTVzkEymACor+Zb55Ie1lRb09VtXuEBdWD6bNZiDfxGVU74rh7fEeb DNGdfCvhn7PaX5fG4UvYeRskTa8P8D1S8tl4g0Aow1dA1Gq+yImOAJn6F9GZLfWHPs88 T62MZIMNd3A9a9bmZY6VbC0gOGH+oHTzTO2K5t4xHMSu8YASPhwpfbM1UClkBC71Imfv Yt4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=rAmbFyk5T+IIgPkQW2TdYk1o+379sHiKmwL7dbbh6IM=; b=Kpcy4Zr/MtcqjVsmE7jq+e9PNdZ+Bf5ficUkH6I/Vw4FGYGeVNuaOP9HT2PoieZEhD u+Blahf5H9Q4bIjkNHHlHaRXNtxdEzW4llNrjtO1QMrs//KkWXl/AuTy/r5I+zSLVBhR 6ASa3BuqwZUXTPmRn95OMpN0JoOBFt+7i2MA4z0L5qpLxEGBNxEcDRVgiicSBgNdYQgc 5S4fR+GyBvMD7251wiR7PYl3HtdlA+Te8vyyM9pOmxQyYIw3WBqbWBQx8i1apiK5TC3b Ful2uXCBlgceEqeM/SLhm/4E65cNT6VfYyYRQm9sE24R71Luy0Mdoo+w51L8g51m1Wel taJw== X-Gm-Message-State: AOAM530CvxOyXU1CpG9xGvzyN76JhOwIdPJ03Ymb3mmNpyUk/UDnsYFc O4RruHGWffnf1XrRxEr2nSQ= X-Google-Smtp-Source: ABdhPJzY+pr+VpcCIFZV41Z1rE7qLAUmBVzRlOd4OgMKTuhx41M72bxb71iVEsdfG0NrzmAaSWZVOw== X-Received: by 2002:a05:600c:3591:: with SMTP id p17mr30737092wmq.134.1630279674464; Sun, 29 Aug 2021 16:27:54 -0700 (PDT) Original-Received: from [192.168.0.6] ([46.251.119.176]) by smtp.googlemail.com with ESMTPSA id u16sm13405441wmc.41.2021.08.29.16.27.53 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 29 Aug 2021 16:27:54 -0700 (PDT) In-Reply-To: <87bl5hm5qj.fsf@gmail.com> Content-Language: en-US X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:212986 Archived-At: On 29.08.2021 03:53, João Távora wrote: > * In what new UI parts is the augmented information to be useful? > > Currently, I see only one place, the diagnostic listing buffer > obtained by M-x flymake-show-diagnostics-buffer. That buffer is > usually associated with only one source buffer > (flymake--diagnostics-buffer-source). Now it should start listing all > the diagnostics for buffers or files known to belong to the same > project, using 'project.el' functionality for that. From what I know of this feature is usually organized, we have two possible kinds of sources of errors: 1. Per buffer, which is currently being edited. 2. For the whole project, where the notion of project is defined by the tool which produces the said list of errors. With that approach, when you fix an error which triggered some cascading errors in other files, you can see those other errors fixed too. Is the idea to build a list of "project errors" using sources of type 1? That would seem inefficient, though I suppose some people might want this too. But I thought the original discussion was about errors from sources of type 2? Then the whole list provided by the source already belongs to the same project (how the LSP server understands it, if we use the LSP example). Is there a need for further filtering?