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.bugs Subject: bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'? Date: Mon, 18 Sep 2023 20:29:45 +0300 Message-ID: <83edive6eu.fsf@gnu.org> References: <1f9e98be-3248-56cf-b7fd-8301666675c6@gmail.com> <1e19cc18-9942-aa51-c49e-9441e873f037@gmail.com> <83edivg3rg.fsf@gnu.org> <83zg1jemi8.fsf@gnu.org> <83sf7beemv.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33501"; mail-complaints-to="usenet@ciao.gmane.io" Cc: jporterbugs@gmail.com, 66041@debbugs.gnu.org To: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Sep 18 19:31:16 2023 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 1qiI5Z-0008Tl-G6 for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 18 Sep 2023 19:31:13 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qiI5K-0004bB-Dn; Mon, 18 Sep 2023 13:30:58 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qiI5G-0004A7-BZ for bug-gnu-emacs@gnu.org; Mon, 18 Sep 2023 13:30:54 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qiI5G-0004we-1r for bug-gnu-emacs@gnu.org; Mon, 18 Sep 2023 13:30:54 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qiI5O-0001Kj-91 for bug-gnu-emacs@gnu.org; Mon, 18 Sep 2023 13:31:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 18 Sep 2023 17:31:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 66041 X-GNU-PR-Package: emacs Original-Received: via spool by 66041-submit@debbugs.gnu.org id=B66041.16950582044955 (code B ref 66041); Mon, 18 Sep 2023 17:31:02 +0000 Original-Received: (at 66041) by debbugs.gnu.org; 18 Sep 2023 17:30:04 +0000 Original-Received: from localhost ([127.0.0.1]:54306 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qiI4R-0001Hq-KD for submit@debbugs.gnu.org; Mon, 18 Sep 2023 13:30:04 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53558) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qiI4P-0001Gu-Fx for 66041@debbugs.gnu.org; Mon, 18 Sep 2023 13:30:02 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qiI4B-0004aD-7W; Mon, 18 Sep 2023 13:29:47 -0400 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=vUZ7rV3JFWB6kW+RIh7OhsaW7YycQf/tZomgK1NFAaY=; b=LWibQ6Qq7qrpZctzpAgq 8OYLJ/ZHMavuqylO7tDIT8FUb8ASPIzQ93P0SQHspuXGuElYLkfxjciHgzvY+OkQPQKx0PVHXTx9k rJDITjWKcbZ9nLMUfU74eAO/L9tUZXSD+EzWluPl+sx4e+cg2WGJOqqz/XksvlYjlvbFwb/ZDQERl 0omNGp0e5BN/4q+yKDx7CH4MBQBJ8Kax6lqHYDONrUjkUshPrflZ2RuaE44yu/HcwGZx0CfaypwET ILrn9hRSo+hwR+YzL++mwYaaoF7w7fkXwyIh+oRunUPQtuYa5xCZLNAamzmJ1Y0cfAsF5oT8QGll4 pAfC2+Vr3dv58w==; In-Reply-To: (message from =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= on Mon, 18 Sep 2023 16:31:45 +0100) 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:270830 Archived-At: > From: João Távora > Date: Mon, 18 Sep 2023 16:31:45 +0100 > Cc: jporterbugs@gmail.com, 66041@debbugs.gnu.org > > On Mon, Sep 18, 2023 at 3:32 PM Eli Zaretskii wrote: > > > > I guess you want the cursor on the first character of the > > overlay-string that is displayed first (leftmost)? Are you asking how > > to implement this when there are more than one overlay at EOB? > > Yes, a direct answer to that question would be nice to know, too. Give your overlays different priorities, and use (cursor t) only in the overlay of the highest priority. If they all have before-string (which is what I saw in the example), then priority will determine which overlay is processed first (and thus displayed first). > The idea is to have multiple bits of diagnostic text displayed > after the end-of-line each related to a source overlay contained > within that line. The idea of the feature is that source overlay > and eol text are linked. If the source overlay is deleted, the > end-of-line should disappear. > > It's similar to what happens with a simple 'after-string' overlay > property, but with the 'after-string' skipping over all characters > until the end of line. > > Currently, I'm doing this with a single "end-of-line" overlay placed > as I explained properly (modulo bugs like this one, of course, since > I intended a single overlay but unexpectedly got two). It's this > second end-of-line overlay which has an 'after-string' property. I use > after change functions to control the value of this property, so that > if a source overlays gets destroyed, the corresponding text in value > is deleted (and eventually also > > But I could probably use multiple end-of-line overlays, with a > one-to-one correspondence to the source overlays. I've tried that too > but abandoned it for difficulty in placing the cursor (similar problem > to this one). > > And I think I tried an overlay modification hook instead of buffer after > change functions and abandoned it too for some reason. Maybe the > modification hook isn't called at all when the overlay is completely > deleted? > > Or, conceivably, it could be done without end-of-line overlays at all, > if somehow a 'eol-string' property similar to 'after-string' was > implemented in the C code. But I would prefer a Lisp solution, of > course. > > So, in summary, there is a fair bit of design space for this feature > (which exists in VS code, btw) and I wanted to know your thoughts > on these possibilities and my decisions. Is placing the cursor the only problem you need to solve? And do I understand correctly that you normally collect all the diagnostics into a single sting, and display it as a single overlay string?