[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#27229: eldoc wrong highlighting for "when"
From: |
Eli Zaretskii |
Subject: |
bug#27229: eldoc wrong highlighting for "when" |
Date: |
Tue, 03 May 2022 14:03:32 +0300 |
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: andrewjmoreton@gmail.com, 27229@debbugs.gnu.org
> Date: Tue, 03 May 2022 11:05:02 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > So now "C-h f when" says
> >
> > (when COND &rest BODY)
> >
> > where it previously said
> >
> > (when COND BODY...)
> >
> > Isn't this a regression?
>
> In what way? We have &rest BODY all over the place, and it's the
> correct syntax to specify that there's a body, so I don't understand
> what you mean.
But when and unless aren't functions, they are "special forms". So
using &rest there is less self-explanatory for those who aren't
necessarily privy to the internals.
IOW, the removed (fn ..." stuff was there for a reason. The original
bug report here wasn't about how we display the doc string, it was
about what eldoc does. So IMO the fix should have been in eldoc,
which would also avoid this negative effect.
- bug#27229: eldoc wrong highlighting for "when", Lars Ingebrigtsen, 2022/05/02
- bug#27229: eldoc wrong highlighting for "when", Eli Zaretskii, 2022/05/02
- bug#27229: eldoc wrong highlighting for "when", Lars Ingebrigtsen, 2022/05/03
- bug#27229: eldoc wrong highlighting for "when",
Eli Zaretskii <=
- bug#27229: eldoc wrong highlighting for "when", Lars Ingebrigtsen, 2022/05/03
- bug#27229: eldoc wrong highlighting for "when", Eli Zaretskii, 2022/05/03
- bug#27229: eldoc wrong highlighting for "when", Lars Ingebrigtsen, 2022/05/03
- bug#27229: eldoc wrong highlighting for "when", Eli Zaretskii, 2022/05/03
- bug#27229: eldoc wrong highlighting for "when", Lars Ingebrigtsen, 2022/05/04
- bug#27229: eldoc wrong highlighting for "when", Eli Zaretskii, 2022/05/04
- bug#27229: eldoc wrong highlighting for "when", Lars Ingebrigtsen, 2022/05/04
- bug#27229: eldoc wrong highlighting for "when", Richard Stallman, 2022/05/04