emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] emacs-25 a541c21: Clarify documentation of 'bufferpos-to-f


From: Eli Zaretskii
Subject: [Emacs-diffs] emacs-25 a541c21: Clarify documentation of 'bufferpos-to-filepos' and 'filepos-to-bufferpos'
Date: Sun, 5 Feb 2017 19:52:07 +0000 (UTC)

branch: emacs-25
commit a541c21e864112267126b1388d4d8553ec294b00
Author: Eli Zaretskii <address@hidden>
Commit: Eli Zaretskii <address@hidden>

    Clarify documentation of 'bufferpos-to-filepos' and 'filepos-to-bufferpos'
    
    * doc/lispref/nonascii.texi (Text Representations): Clarify that
    'exact' value of QUALITY argument to 'bufferpos-to-filepos' and
    'filepos-to-bufferpos' can lead to expensive and slow processing.
    
    * lisp/international/mule-util.el (filepos-to-bufferpos)
    (bufferpos-to-filepos): Doc fix.  (Bug#25626)
---
 doc/lispref/nonascii.texi       |    2 +-
 lisp/international/mule-util.el |    4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/lispref/nonascii.texi b/doc/lispref/nonascii.texi
index e3cb5d0..2c3e6ef2 100644
--- a/doc/lispref/nonascii.texi
+++ b/doc/lispref/nonascii.texi
@@ -142,7 +142,7 @@ be one of the following:
 @table @code
 @item exact
 The result must be accurate.  The function may need to encode and
-decode a large part of the buffer.
+decode a large part of the buffer, which is expensive and can be slow.
 @item approximate
 The value can be an approximation.  The function may avoid expensive
 processing and return an inexact result.
diff --git a/lisp/international/mule-util.el b/lisp/international/mule-util.el
index 06b63ea..7657e40 100644
--- a/lisp/international/mule-util.el
+++ b/lisp/international/mule-util.el
@@ -352,7 +352,7 @@ QUALITY can be:
   `approximate', in which case we may cut some corners to avoid
     excessive work.
   `exact', in which case we may end up re-(en/de)coding a large
-    part of the file/buffer.
+    part of the file/buffer, this can be expensive and slow.
   nil, in which case we may return nil rather than an approximation."
   (unless coding-system (setq coding-system buffer-file-coding-system))
   (let ((eol (coding-system-eol-type coding-system))
@@ -428,7 +428,7 @@ QUALITY can be:
   `approximate', in which case we may cut some corners to avoid
     excessive work.
   `exact', in which case we may end up re-(en/de)coding a large
-    part of the file/buffer.
+    part of the file/buffer, this can be expensive and slow.
   nil, in which case we may return nil rather than an approximation."
   (unless coding-system (setq coding-system buffer-file-coding-system))
   (let* ((eol (coding-system-eol-type coding-system))



reply via email to

[Prev in Thread] Current Thread [Next in Thread]