unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: "João Távora" <joaotavora@gmail.com>, "Eli Zaretskii" <eliz@gnu.org>
Cc: 66041@debbugs.gnu.org
Subject: bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'?
Date: Mon, 25 Sep 2023 13:55:19 -0700	[thread overview]
Message-ID: <b49e08e8-df98-be70-8e4a-e6d1e7d02ce2@gmail.com> (raw)
In-Reply-To: <CALDnm52mv=KaECCSx=89iwyYE3SU8wsuk-8kc+AbyGJ4WbSOZg@mail.gmail.com>

On 9/25/2023 11:23 AM, João Távora wrote:
> On Mon, Sep 25, 2023 at 6:24 PM Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> 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.

This may or may not be helpful, but back in commit b87400c78b04, I added 
the ability to specify the particular bitmap to use for a fringe icon. 
For example, you can set 'bookmark-fringe-mark' to any known fringe 
bitmap, and then you'll see that bitmap in the fringe for your 
bookmarks. In essence, this lets you split the semantic meaning for a 
fringe marker ("this marker means there's a bookmark here") from the 
actual bitmap data ("what it looks like").

There's probably room to expand this convention from bookmarks to other 
parts of Emacs, and maybe Flymake could benefit from it.





      reply	other threads:[~2023-09-25 20:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-17  4:42 bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'? Jim Porter
2023-09-17 21:22 ` João Távora
2023-09-17 21:54   ` Jim Porter
2023-09-17 22:15     ` João Távora
2023-09-18  4:36       ` Jim Porter
2023-09-18 10:44       ` Eli Zaretskii
2023-09-18 10:46         ` João Távora
2023-09-18 11:42           ` Eli Zaretskii
2023-09-18 12:52             ` João Távora
2023-09-18 14:32               ` Eli Zaretskii
2023-09-18 15:31                 ` João Távora
2023-09-18 17:29                   ` Eli Zaretskii
2023-09-18 18:55                     ` João Távora
2023-09-18 17:44               ` Jim Porter
2023-09-18 18:49                 ` João Távora
2023-09-18 19:00                   ` Jim Porter
2023-09-21 21:40                   ` João Távora
2023-09-24  3:38                     ` Jim Porter
2023-09-24  8:18                       ` João Távora
2023-09-25  8:59                         ` João Távora
2023-09-25 10:32                           ` Eli Zaretskii
2023-09-25 11:46                             ` João Távora
2023-09-25 12:08                               ` Eli Zaretskii
2023-09-25 12:12                                 ` João Távora
2023-09-25 12:49                                   ` Eli Zaretskii
2023-09-25 13:52                                     ` João Távora
2023-09-25 14:19                                       ` Eli Zaretskii
2023-09-25 16:55                                         ` João Távora
2023-09-25 17:23                                           ` Eli Zaretskii
2023-09-25 18:23                                             ` João Távora
2023-09-25 20:55                                               ` Jim Porter [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b49e08e8-df98-be70-8e4a-e6d1e7d02ce2@gmail.com \
    --to=jporterbugs@gmail.com \
    --cc=66041@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=joaotavora@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).