Line 5977 of the eval.txt helpfile says:
%G floating point number, as %f or %E depending on value
This is ambiguous if the value is NaN or ±INF: is the result in upper
case (as for %E) or in lower case (as for %f)? I propose to replace %f
by %F in that line to remove the ambiguity, as experiment shows that,
for instance, printf('%G', 1.0/0) is output as INF not inf.
I'm attaching, for your convenience, a patch for the proposed change.
Best regards,
Tony.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
--- a/runtime/doc/eval.txt 2017-01-29 00:38:48.758677458 +0100
+++ b/runtime/doc/eval.txt 2017-01-29 12:24:26.869741766 +0100
@@ -5969,17 +5969,17 @@
%X hex number using upper case letters
%o octal number
%08b binary number padded with zeros to at least 8 chars
%f floating point number as 12.23, inf, -inf or nan
%F floating point number as 12.23, INF, -INF or NAN
%e floating point number as 1.23e3, inf, -inf or nan
%E floating point number as 1.23E3, INF, -INF or NAN
%g floating point number, as %f or %e depending on value
- %G floating point number, as %f or %E depending on value
+ %G floating point number, as %F or %E depending on value
%% the % character itself
Conversion specifications start with '%' and end with the
conversion type. All other characters are copied unchanged to
the result.
The "%" starts a conversion specification. The following
arguments appear in sequence:
