From: Tino Calancha <tino.calancha@gmail.com>
Date: Fri, 22 Jul 2016 07:45:51 +0000 (+0900)
Subject: Update define-ibuffer-op doc string
X-Git-Tag: emacs-26.0.90~1840^2~21
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=c608f4901af65e9451fba1ca8f03f6d43bfc1ecc;p=emacs.git

Update define-ibuffer-op doc string

* lisp/ibuf-macs.el (define-ibuffer-op): Document arg COMPLEX
instead of refer the reader to the source code.
Document arg BODY.
---

diff --git a/lisp/ibuf-macs.el b/lisp/ibuf-macs.el
index 2f4d50d9a3e..2411f0588e3 100644
--- a/lisp/ibuf-macs.el
+++ b/lisp/ibuf-macs.el
@@ -198,8 +198,12 @@ operation is complete, in the form:
 ACTIVE-OPSTRING is a string which will be displayed to the user in a
 confirmation message, in the form:
  \"Really ACTIVE-OPSTRING x buffers?\"
-COMPLEX means this function is special; see the source code of this
-macro for exactly what it does.
+COMPLEX means this function is special; if COMPLEX is nil BODY
+evaluates once for each marked buffer, MBUF, with MBUF current
+and saving the point.  If COMPLEX is non-nil, BODY evaluates
+without requiring MBUF current.
+BODY define the operation; they are forms to evaluate per each
+marked buffer.
 
 \(fn OP ARGS DOCUMENTATION (&key INTERACTIVE MARK MODIFIER-P DANGEROUS OPSTRING ACTIVE-OPSTRING COMPLEX) &rest BODY)"
   (declare (indent 2) (doc-string 3))