summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2016-08-26 22:13:34 +0300
committerEli Zaretskii <eliz@gnu.org>2016-08-26 22:13:34 +0300
commit80a7f8be7bca1ca488887eedd7f0022d088e124a (patch)
treeeafb6497dbdfe92ef5e68262ece11e3cc255986d
parent88a5052579069be93a0af556c9a43a8ed75d3efb (diff)
downloademacs-80a7f8be7bca1ca488887eedd7f0022d088e124a.tar.gz
Clarify documentation of precision in format specs
* doc/lispref/strings.texi (Formatting Strings): Be less definitive wrt what precision means in format specs other than floating-point, %s and %S. (Bug#24314)
-rw-r--r--doc/lispref/strings.texi5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/lispref/strings.texi b/doc/lispref/strings.texi
index febe3212ba9..5fee37361fd 100644
--- a/doc/lispref/strings.texi
+++ b/doc/lispref/strings.texi
@@ -1052,8 +1052,9 @@ precision specifies how many decimal places to show; if zero, the
decimal-point itself is also omitted. For @samp{%s} and @samp{%S},
the precision truncates the string to the given width, so @samp{%.3s}
shows only the first three characters of the representation for
-@var{object}. Precision has no effect for other specification
-characters.
+@var{object}. For other specification characters, the effect of
+precision is what the local library functions of the @code{printf}
+family produce.
@node Case Conversion
@section Case Conversion in Lisp