[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#28070: 24.5; doc string of `eval-buffer'
From: |
Lars Ingebrigtsen |
Subject: |
bug#28070: 24.5; doc string of `eval-buffer' |
Date: |
Mon, 15 Jul 2019 19:39:31 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#28070: 24.5; doc string of `eval-buffer',
Lars Ingebrigtsen <=