[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: rethinking @def*
From: |
Eli Zaretskii |
Subject: |
Re: rethinking @def* |
Date: |
Tue, 26 Jul 2022 15:29:12 +0300 |
> Date: Tue, 26 Jul 2022 11:31:27 +0000 (UTC)
> Cc: bug-texinfo@gnu.org
> From: Werner LEMBERG <wl@gnu.org>
>
>
> > Here is a proposal: [...]
>
> ... I consider this a bad idea. Whatever you are going to change, it
> will be backward incompatible, causing a lot of grief. For example,
> the adjustments to document troff commands (in the groff info manual)
> are quite tricky, trying very hard to overcome the various limitations
> and formatting issues of `@def` and friends.
>
> I thus strongly suggest that you implement *new* commands, say,
> `@define`, `@define*`, etc., that have better semantics.
I tend to agree, FWIW. We could then slowly migrate to the new
commands and encourage others to do so.
- rethinking @def*, Patrice Dumas, 2022/07/26
- Re: rethinking @def*, Werner LEMBERG, 2022/07/26
- Re: rethinking @def*, pertusus, 2022/07/26
- Re: rethinking @def*, Werner LEMBERG, 2022/07/26
- Re: rethinking @def*, pertusus, 2022/07/26
- Re: rethinking @def*, Werner LEMBERG, 2022/07/26