Follow-up Comment #6, bug #59608 (project groff):
[comment #5 comment #5:]
> 1) Mark significant trailing space as such, that is not just "...abc \"
> but
> "...abc \"significant trailing space
>
> Marking significant trailing space with just the slash-quote follows the
recommendation made by Werner some years ago. With nothing after it, it
already means "the foregoing space is significant." Adding the comment
afterwards would be tautological.
>
If the reader already recognizes its meaning.
That does not apply to readers,
that see such a "construct" for the first time,
or have forgotten what it is supposed to mean.
I find an explicit "warning text (sign)" better and more future proof.
N.B. Starting each sentence on a new line is better to make clear to
what part an answer applies to.
> Not sure what you mean by "2) Show all arguments in a diagnostic message."
Do you mean every argument that was passed to the macro? What would be the
advantage? A user needs
a) Every argument
b) The reader sees all (variable) information;
otherwise it is obscured (censored).
Adding one line to all instances is simpler
than to edit each relevant line.
.tm The arguments are: \\@
>only know the offending calling macro, its position in the file, which arg is
bad ("first," "second"... or "arg to <keyword"), and why.
How do you know in advance,
what a user needs to fix the error in the shortest time.
The content of an argument is now not always shown.
> Listing additional correct arguments serves no purpose and could, in some
instances, add a huge amount noise. Some of the _STYLE macros have over ten
keyword/value pairs as arguments.
The number of arguments to be displayed does not matter,
their content could.
The simplest cure as stated above:
add a single line to all diagnostic blocks,
like
.tm The arguments are: \\@
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?59608>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
