Re: master 48aacbf292 2/2: Make many seldom-used generalized variables obsolete

[Ihor Radchenko <yantar92@gmail.com>]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> "Basil L. Contovounesios" <contovob@tcd.ie> writes:
>
>> If frame-height is obsolete, frame-width should be as well, right?
>
> Yup.  Now done.

This commit also obsoleted a number of generalized variables used by
Org. In particular, `buffer-substring', and `buffer-string'.

While it is indeed possible to set buffer contents without the above
variables, it cannot (AFAIK) be done using a single function call.
Would it be possible to provide a function replacement for setting a
buffer text in the whole buffer/buffer region?

Also, obsoleting `buffer-file-name' revealed one potentially concerning
fact about generalized variables. The expansion of `buffer-file-name'
setter, `set-visited-file-name' "... also renames the buffer to
correspond to the new file." I am now wondering if there are any
non-obvious side effects when using other generalized variables - there
is (AFAIK) no documentation about what exactly various setters for
generalized variables do other than occasional paragraph in the manual.

-- 
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92