all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jporterbugs@gmail.com, 66041@debbugs.gnu.org
Subject: bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'?
Date: Mon, 25 Sep 2023 13:12:50 +0100	[thread overview]
Message-ID: <CALDnm50ExwS2P15xsc2rtaTbdy8kQ0gSWQKpXgbZ_tgSdYprJA@mail.gmail.com> (raw)
In-Reply-To: <831qem316n.fsf@gnu.org>

On Mon, Sep 25, 2023 at 1:09 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: João Távora <joaotavora@gmail.com>
> > Date: Mon, 25 Sep 2023 12:46:35 +0100
> > Cc: jporterbugs@gmail.com, 66041@debbugs.gnu.org
> >
> > On Mon, Sep 25, 2023 at 11:32 AM Eli Zaretskii <eliz@gnu.org> wrote:
> >
> > > Add some character after the SPC, even a newline, and the display will
> > > be as you expect.
> >
> > I think that's only because this newline will, by default, delete the SPC
> > character and thus resolve the diagnostic from checkdoc, deleting the
> > overlay.
>
> No, because if you insert any other character after the space, the
> display will also be as you expect.

Obviously, because any other character which is not space
will _also_ fix the trailing whitespace diagnostic issued by the
checkdoc backend. By definition :-)

I can give a more complicated recipe using the Eglot and LSP
if you want, but it will require you install 'clangd'.

João





  reply	other threads:[~2023-09-25 12:12 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 [this message]
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

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

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

  git send-email \
    --in-reply-to=CALDnm50ExwS2P15xsc2rtaTbdy8kQ0gSWQKpXgbZ_tgSdYprJA@mail.gmail.com \
    --to=joaotavora@gmail.com \
    --cc=66041@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jporterbugs@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.