* bug#28070: 24.5; doc string of `eval-buffer'
@ 2017-08-12 22:45 Drew Adams
2019-07-15 17:39 ` Lars Ingebrigtsen
0 siblings, 1 reply; 2+ messages in thread
From: Drew Adams @ 2017-08-12 22:45 UTC (permalink / raw)
To: 28070
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'
^ permalink raw reply [flat|nested] 2+ messages in thread
* bug#28070: 24.5; doc string of `eval-buffer'
2017-08-12 22:45 bug#28070: 24.5; doc string of `eval-buffer' Drew Adams
@ 2019-07-15 17:39 ` Lars Ingebrigtsen
0 siblings, 0 replies; 2+ messages in thread
From: Lars Ingebrigtsen @ 2019-07-15 17:39 UTC (permalink / raw)
To: Drew Adams; +Cc: 28070
Drew Adams <drew.adams@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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-07-15 17:39 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-08-12 22:45 bug#28070: 24.5; doc string of `eval-buffer' Drew Adams
2019-07-15 17:39 ` Lars Ingebrigtsen
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).