GNU bug report logs - #28070
24.5; doc string of `eval-buffer'

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 28070 in the body.
You can then email your comments to 28070 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.5; doc string of `eval-buffer'
Date: Sat, 12 Aug 2017 15:45:25 -0700 (PDT)

The doc string should, like Elisp manual node `Eval', mention that this
does NOT always "Execute the current buffer as Lisp code."  It acts on the current buffer restriction, if any.

As the manual says:

  `eval-buffer' operates on the entire accessible portion of buffer
                                       ^^^^^^^^^^^^^^^^^^

That qualification changes everything.  We don't always need to point
out explicitly that a particular function acts on the accessible portion
of the buffer, but it is important to do so in this case.

In GNU Emacs 24.5.1 (i686-pc-mingw32)
 of 2015-04-11 on LEG570
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=3D/c/usr --host=3Di686-pc-mingw32'

Message #8 received at 28070 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 28070 <at> debbugs.gnu.org
Subject: Re: bug#28070: 24.5; doc string of `eval-buffer'
Date: Mon, 15 Jul 2019 19:39:31 +0200

Drew Adams <drew.adams <at> oracle.com> writes:

> The doc string should, like Elisp manual node `Eval', mention that this
> does NOT always "Execute the current buffer as Lisp code."  It acts on the current buffer restriction, if any.
>
> As the manual says:
>
>   `eval-buffer' operates on the entire accessible portion of buffer
>                                        ^^^^^^^^^^^^^^^^^^
>
> That qualification changes everything.  We don't always need to point
> out explicitly that a particular function acts on the accessible portion
> of the buffer, but it is important to do so in this case.

Looks like this was fixed in 2015:

---

Execute the accessible portion of current buffer as Lisp code.


-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.