On Fri, Dec 9, 2022 at 11:40 PM Eli Zaretskii <
eliz@gnu.org> wrote:
> From: Gavin Smith <gavinsmith0123@gmail.com>
> Date: Sat, 10 Dec 2022 00:35:19 +0000
>
> > d.texi:2: bad @table argument
>
> would be sufficient. It could be difficult to explain the usage
> of @table in an short error message.
>
> Perhaps if there is no argument at all it could be
>
> > d.texi:2: @table requires an argument
>
> instead, although this wouldn't be necessary.
How about "bad or missing @table argument: 'FOO'" ?
This works for me, except I'd separate out the two cases: "Missing @table argument." and "Bad @table argument: FOO". I think error messages should be as simple and as explicit as possible and provide whatever information that caused it to make it easier for a user to figure out what's going on.