[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation
From: |
João Távora |
Subject: |
bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'? |
Date: |
Mon, 25 Sep 2023 13:12:50 +0100 |
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
- bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'?, (continued)
- bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'?, Jim Porter, 2023/09/18
- bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'?, João Távora, 2023/09/18
- bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'?, Jim Porter, 2023/09/18
- bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'?, João Távora, 2023/09/21
- bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'?, Jim Porter, 2023/09/23
- bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'?, João Távora, 2023/09/24
- bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'?, João Távora, 2023/09/25
- bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'?, Eli Zaretskii, 2023/09/25
- bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'?, João Távora, 2023/09/25
- bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'?, Eli Zaretskii, 2023/09/25
- bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'?,
João Távora <=
- bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'?, Eli Zaretskii, 2023/09/25
- bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'?, João Távora, 2023/09/25
- bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'?, Eli Zaretskii, 2023/09/25
- bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'?, João Távora, 2023/09/25
- bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'?, Eli Zaretskii, 2023/09/25
- bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'?, João Távora, 2023/09/25
- bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'?, Jim Porter, 2023/09/25