From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Newsgroups: gmane.emacs.bugs Subject: bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'? Date: Mon, 25 Sep 2023 19:23:08 +0100 Message-ID: References: <1f9e98be-3248-56cf-b7fd-8301666675c6@gmail.com> <1e19cc18-9942-aa51-c49e-9441e873f037@gmail.com> <83edivg3rg.fsf@gnu.org> <83zg1jemi8.fsf@gnu.org> <8d01b781-abac-e22b-39fe-8697a173ad7a@gmail.com> <834jji35nc.fsf@gnu.org> <831qem316n.fsf@gnu.org> <83zg1a1kq9.fsf@gnu.org> <83v8by1gkr.fsf@gnu.org> <83sf72180i.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1970"; mail-complaints-to="usenet@ciao.gmane.io" Cc: jporterbugs@gmail.com, 66041@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Sep 25 20:24:15 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 1qkqFj-0000GU-HT for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 25 Sep 2023 20:24:15 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qkqFO-0000vl-C0; Mon, 25 Sep 2023 14:23:54 -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 1qkqFK-0000vX-78 for bug-gnu-emacs@gnu.org; Mon, 25 Sep 2023 14:23:51 -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 1qkqFJ-0006fl-VJ for bug-gnu-emacs@gnu.org; Mon, 25 Sep 2023 14:23:49 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qkqFW-00019K-31 for bug-gnu-emacs@gnu.org; Mon, 25 Sep 2023 14:24:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 25 Sep 2023 18:24: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.16956662284394 (code B ref 66041); Mon, 25 Sep 2023 18:24:02 +0000 Original-Received: (at 66041) by debbugs.gnu.org; 25 Sep 2023 18:23:48 +0000 Original-Received: from localhost ([127.0.0.1]:46645 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qkqFE-00018k-Bc for submit@debbugs.gnu.org; Mon, 25 Sep 2023 14:23:48 -0400 Original-Received: from mail-lf1-x133.google.com ([2a00:1450:4864:20::133]:50685) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qkqF9-00018L-BD for 66041@debbugs.gnu.org; Mon, 25 Sep 2023 14:23:43 -0400 Original-Received: by mail-lf1-x133.google.com with SMTP id 2adb3069b0e04-5046bf37daeso1720096e87.1 for <66041@debbugs.gnu.org>; Mon, 25 Sep 2023 11:23:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1695666200; x=1696271000; darn=debbugs.gnu.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=wl8gNlrVbAJcfjFq6feMXpDpYsYdrHXVGxDDXWfhqiw=; b=JWc/Rcv3NKAEhqk5G0CJBfN8dEerZqeRn43gINbn/iDNLh+6znlxq0lkXOAPKs4wrP SJgNoTueuni9OCTy/SPY9kj5JhCL/OH/r733aIf3qlv2qK44+lLQi64IJf7cuYRfS3TY huG+l3TXclZlP+fRqka6/FoHIJ24M9zU1mXAlc+xtFpoczUPKKf2skY+nND6hE+Syxfa 8OWJa+XQK353Gj3JVcS5YZ2ln3wZGFX8DQ5fhKcbLDuk38glJKzJ1mQGGE7uguQY9DMn GdKP2BJd+RQTlM41Nd6xQULyV2H1vFIitn+zzd6/zB+ouASVhmpIQ9VzDkp2CTvN/s17 zHCw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695666200; x=1696271000; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=wl8gNlrVbAJcfjFq6feMXpDpYsYdrHXVGxDDXWfhqiw=; b=P/5D5b3s3cBaoMYl0hNekAFnBtgHvqTn8WB5i8VZAGLloSUawMkP9QzioBuiUQVHiv kQyTTUaJjl2BBHEptBS70RVq5n0gOcRqPR6yh/9oHd/ZQNBQprRWTFUELGABz5KSwCV/ U9wPQuP1sC9UQwabel0gFk8xU5mTFu5M/IkuLQFZxbPs7g5Od4ERyL8AyCGiBK9MO9nm pVeGy0NJUz+KSGGBcvwHj3cunumUG/xbyDHklQSCA9n9qyEP8bqLEX+ZAtVMzuIfYDf2 oOS9xeCKBsi7oJqPKs9gbKl+xvZf+TI6/oeJZScjOJYyuIFSP1xDRA95uwb6PFW0La2Y LakA== X-Gm-Message-State: AOJu0YzCDzZjGWquTKIHNKgTSncxYJa9/29NLMfFYNZrEOMcU5Vejr4H t8WoPq6on/JAgKNYj0Vtm66KNk3IiUGLd3YWBxA= X-Google-Smtp-Source: AGHT+IGbD5uw2cSW5UvpTYVV1NdA5zh5JLZHqQTat3uJVLLnF+MA6hQWeNY/DW96yIvV8MnsVZuNxpRrrtGlKK58i3A= X-Received: by 2002:ac2:5630:0:b0:4f8:7772:3dfd with SMTP id b16-20020ac25630000000b004f877723dfdmr5517176lff.11.1695666199919; Mon, 25 Sep 2023 11:23:19 -0700 (PDT) In-Reply-To: <83sf72180i.fsf@gnu.org> 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:271348 Archived-At: On Mon, Sep 25, 2023 at 6:24=E2=80=AFPM Eli Zaretskii wrote: > > I assume it does, since otherwise that would mean that > > if a line is scrolled near the beginning and truncated, the current > > "last one" criteria you described before also doesn't always > > hold true. > > The "last one" means the last overlay processed on a screen line. Ah, ok: good to know. > > > IMHO this should be automatic and based on relative overlay > > priorities. > > Overlay priorities are not for overlays that cover disjoint portions > of text. Also, the same problem will happen when several 'display' > properties that draw on the fringe are put on buffer text, without any > overlays and thus without any priorities to begin with. True, I forgot about that. > So if we want > to implement something like this in the display engine, we'd need to > extend the format of the 'display' property in this case, adding some > kind of "priority" there, or maybe extend the fringe bitmap data > itself. I think either is acceptable, though the former is slightly better as it allows one to use the same bitmap data in many priorities. Jo=C3=A3o