Thu, Feb 29
Feb 23 2024
I think we should close this bug or re-purpose it to silence those warnings in common cases.
That could be fixed in src/argparse.c:set_opt_arg by adding and endptr to the strtol calls and check that only white space follows. However, there is some risk of regression with this approach. Maybe just display a warning?
With today's release of npth everything should be set.
Feb 6 2024
Feb 1 2024
Thank you for the fix. Pushed the change modifying the commit log for the ChangeLog entry.
Jan 31 2024
Jan 23 2024
Jan 22 2024
Jan 16 2024
Alright.
Push the change as rE4a9def77488f: estream: Fix call to string filter for estream-printf..
I see your point: allocating STRINGBUF to make sure nul-terminated string.
The code itself doesn't work well in a test case of tests/t-prinntf.c, because it assumes string filter should be called with NULL for string.
Jan 15 2024
Like this:
@@ -1196,10 +1196,25 @@ pr_string (estream_printf_out_t outfnc, void *outfncarg, future, when breaking API/ABI is OK, we can change signature of gpgrt_string_filter_t to have another argument for precision. */ int allow_non_nul_string = (arg->precision >= 0); + char *stringbuf = NULL;
We could also pass a nul terminated copy to the filter function in pr_string.
Dec 27 2023
Nov 15 2023
@item handling with @table has been pushed.
Nov 14 2023
I learned about how @item is handled by TeX. By @table command, user specifies how to handle the item line. In the case of GnuPG, it is like:
@table @gnupgtabopt @item --version ... @item --help
(Emacs uses @table @samp, while GCC uses @table @gcctabopt.)
And @gnupgtabopt is a macro which is expanded to @code{\body\}
Nov 8 2023
Possible approach for source texinfo files and yat2m would be:
Nov 2 2023
I found a regression for @item --version; It emits \[en]version for roff.
Pushed my fix to support them.
Oct 5 2023
Sep 30 2023
I guess we should add an extended API to set the filter.