Next: GNU Free Documentation License, Previous: Preparing Lisp code for distribution, Up: Emacs Lisp [Contents][Index]
For those users who live backwards in time, here is information about downgrading to Emacs version 29.4. We hope you will enjoy the greater simplicity that results from the absence of many Emacs 30.1 features.
wheel-up/down
and sometimes
mouse-4/5/6/7
. Lisp programs which use these should once again
be aware of the conventions in effect and behave accordingly.
describe-function
no longer distracts you by showing
unnecessary details like the type of the function’s object. Emacs
hackers always know whether a function is a primitive, a native-compiled
Lisp function, or any other kind. Stating the obvious simply wastes the
precious screen estate; as you move into the past, and the typical
dimensions of the screen become smaller, that waste is less and less
justified. So we made the waste smaller.
minibuffer-regexp-mode
was removed. Regular expressions are
just strings, so no fancy mode should be needed for editing them.
\x
without any following hex digits
as character code zero (NUL), as it always was in Emacs. The
savings in typing due to this alone are enough to justify this
simplification.
value<
function and
keyword arguments for sort
, were deleted as too complex. The
basic sort
function should all that’s needed in the years to go.
provided-mode-derived-p
, derived-mode-add-parents
, and
others. We decided that untangling the mode inheritance relationships
by hand facilitates more clear code and makes the intent evident.
declare
forms for functions, such as
ftype
. Emacs Lisp is not a string-typed language, which makes
these declarations anathema. The types closure
and
interpreted-function
are gone for the same reason: no need to
distinguish types of Lisp functions.
lexical-binding
cookies, empty bodies of special forms and
macros, comparison with literals, condition-case
without
handlers, mutation of constants, and some others. As time moves into
the past, the typical Emacs hacker knows best what’s correct code and
what isn’t, and thus these warnings become useless annoyances. Good
riddance!
obarray
type is gone. Obarrays are back to their original
representation as vectors. Each removed Lisp data type makes Emacs
simpler and easier to use, so this is a welcome deletion.
Next: GNU Free Documentation License, Previous: Preparing Lisp code for distribution, Up: Emacs Lisp [Contents][Index]