all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Gregor Zattler <grfz@gmx.de>
To: 12629@debbugs.gnu.org
Subject: bug#12629: 24.2.50; [Doc][PATCH] Neither `what-line' nor `count-lines' do call the respectiv other in recent GNU/Emacs.
Date: Fri, 12 Oct 2012 19:48:44 +0200	[thread overview]
Message-ID: <87wqyvtwcj.fsf@boo.workgroup> (raw)

Dear Emacs developers,

is "Introduction to Programming in Emacs Lisp" written by Robert
J. Chassell, still updated?  There is an error in it, this patch
corrects it.

---
 doc/lispintro/emacs-lisp-intro.texi |    7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/doc/lispintro/emacs-lisp-intro.texi b/doc/lispintro/emacs-lisp-intro.texi
index 04e3e0c..6d3a5d0 100644
--- a/doc/lispintro/emacs-lisp-intro.texi
+++ b/doc/lispintro/emacs-lisp-intro.texi
@@ -6600,10 +6600,9 @@ buffer; or conversely, an Emacs Lisp function needs to work on all of a
 buffer that has been narrowed.  The @code{what-line} function, for
 example, removes the narrowing from a buffer, if it has any narrowing
 and when it has finished its job, restores the narrowing to what it was.
-On the other hand, the @code{count-lines} function, which is called by
-@code{what-line}, uses narrowing to restrict itself to just that portion
-of the buffer in which it is interested and then restores the previous
-situation.
+On the other hand, the @code{count-lines} function uses narrowing to
+restrict itself to just that portion of the buffer in which it is
+interested and then restores the previous situation.
 
 @node save-restriction
 @section The @code{save-restriction} Special Form
-- 
1.7.10.4





             reply	other threads:[~2012-10-12 17:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12 17:48 Gregor Zattler [this message]
2012-10-13  2:23 ` bug#12629: 24.2.50; [Doc][PATCH] Neither `what-line' nor `count-lines' do call the respectiv other in recent GNU/Emacs Glenn Morris

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wqyvtwcj.fsf@boo.workgroup \
    --to=grfz@gmx.de \
    --cc=12629@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.