From: Eli Zaretskii <eliz@gnu.org>
To: Elijah G <eg642616@gmail.com>, Spencer Baugh <sbaugh@janestreet.com>
Cc: joaotavora@gmail.com, philipk@posteo.net, emacs-devel@gnu.org
Subject: Re: [PATCH] Flymake Support Indicator Errors in Margin
Date: Sat, 16 Mar 2024 13:10:14 +0200 [thread overview]
Message-ID: <864jd677qh.fsf@gnu.org> (raw)
In-Reply-To: <CACnP4NJgW8G6RJdu-W-fCMgGEey3eL9EErFBgMn8jd8=E9LMiw@mail.gmail.com> (message from Elijah G on Thu, 14 Mar 2024 09:35:33 -0600)
> From: Elijah G <eg642616@gmail.com>
> Date: Thu, 14 Mar 2024 09:35:33 -0600
> Cc: João Távora <joaotavora@gmail.com>,
> philipk@posteo.net, emacs-devel@gnu.org
>
> On Thu, Mar 14, 2024 at 5:05 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > > +(defcustom flymake-margin-indicators-string
> > > + `((error ,(if (char-displayable-p 8252)
> > > + "‼"
> > > + "!!")
> > > + compilation-error)
> >
> > When do you expect this value to be evaluated?
> >
> > In general, I wonder whether it would be simpler and wiser to use just
> > "!!", and leave it to users to customize to "‼" if their displays
> > support that. (We can mention the possibility in the doc string.)
>
> I implemented it in a similar way to how display-fill-column-indicator
> does with display-fill-column-indicator-character, this since I expect
> users to only set left-margin-width to 1, because if there is several
> errors on the same line, the indicators will be displayed next to each
> other and it could be confusing.
>
> However I agree that it is better to change it to just "!!",
> I fixed the patch and added a doc string for the possibility of including
> non-ASCII characters.
Spencer, any comments?
next prev parent reply other threads:[~2024-03-16 11:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 23:18 [PATCH] Flymake Support Indicator Errors in Margin Elijah G
2024-03-12 9:24 ` Philip Kaludercic
2024-03-12 17:22 ` Elijah G
2024-03-13 12:18 ` Eli Zaretskii
2024-03-14 1:50 ` Elijah G
2024-03-14 11:05 ` Eli Zaretskii
2024-03-14 11:28 ` João Távora
2024-03-14 15:35 ` Elijah G
2024-03-16 11:10 ` Eli Zaretskii [this message]
2024-03-17 16:44 ` bird
2024-03-17 17:01 ` Eli Zaretskii
2024-03-17 17:34 ` Elijah G
2024-03-17 18:43 ` bird
2024-03-17 19:21 ` Elijah G
2024-03-25 1:46 ` Elijah G
2024-03-27 0:13 ` sbaugh
2024-03-27 0:36 ` Elijah G
2024-03-27 21:29 ` Elijah G
2024-03-28 6:01 ` Eli Zaretskii
2024-03-28 17:34 ` Elijah G
2024-04-06 11:36 ` Eli Zaretskii
2024-03-28 7:30 ` Juri Linkov
2024-03-28 17:44 ` Elijah G
2024-04-06 11:35 ` Eli Zaretskii
2024-04-06 20:14 ` Elijah G
2024-04-07 5:47 ` Eli Zaretskii
2024-04-07 17:20 ` Elijah G
2024-04-18 9:10 ` Eli Zaretskii
2024-03-19 7:03 ` Augusto Stoffel
2024-03-17 17:49 ` Elijah G
2024-03-19 7:04 ` Augusto Stoffel
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=864jd677qh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eg642616@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=philipk@posteo.net \
--cc=sbaugh@janestreet.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).