Re: [toggle-read-only] (was: replacement of find-file-not-found-hooks)

[Eli Zaretskii <eliz@gnu.org>]

> From: Uwe Brauer <oub@mat.ucm.es>
> Cc: Uwe Brauer <oub@mat.ucm.es>, philipk@posteo.net,
> 	stefankangas@gmail.com, rms@gnu.org, emacs-devel@gnu.org
> Date: Wed, 24 Jul 2024 14:33:35 +0200
> 
> >> 2. When I compile I of course see the warnings, but do you suggest
> >> that I just byte compile all my files after installing a new
> >> Emacs version?
> 
> > Yes, I'd definitely recommend that.  I do it myself on my systems,
> > FWIW.
> 
> Oh my god, that will also end up taking me days.

Why "days"? how many Lisp files do you have that it could take "days"
top byte-compile them?

> BTW, code, that worked in emacs 28 now gave an error because
> toggle-read-only is no longer known to be defined and here no hint
> was given what to use
> 
> So I boldly 
> replaced
> -		  (toggle-read-only nil))
> by
> +		  (read-only-mode nil))
> 
> It worked

toggle-read-only is obsolete since Emacs 24, i.e. for the last 12
years.

> >> 3. I still find the naming «find-file-not-found-functions»
> >> and therefore the call
> >> (add-hook 'find-file-not-found-functions
> >> 'insert-auto-insert-files 'append)
> >> counterintuitive, (now it is too late, but why wasn't this called
> >> «find-file-not-found-hook-functions» or something like this).
> 
> > Longer names are harder to type and read.
> 
> Yeah but maybe easier to find via apropos!

No, not easier.

> >> 5. I still don't gasp the advantage of renaming functions and
> >> variables. I understand the benefit of introducing  new functions and
> >> variables but the benefit of renaming variables and functions I
> >> fail to see.
> 
> > It makes Emacs easier to learn and use.
> 
> And it breaks backward compatibility.

Which is why we do it very sparingly and always after a very long
period of obsolescence.  Many people think we are too conservative.