From: Philip Kaludercic <philipk@posteo.net>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: Stefan Kangas <stefankangas@gmail.com>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: replacement of find-file-not-found-hooks
Date: Tue, 23 Jul 2024 08:41:12 +0000 [thread overview]
Message-ID: <87o76ojyaf.fsf@posteo.net> (raw)
In-Reply-To: <877cdc8us0.fsf@mat.ucm.es> (Uwe Brauer's message of "Tue, 23 Jul 2024 08:52:31 +0200")
Uwe Brauer <oub@mat.ucm.es> writes:
>>>> "SK" == Stefan Kangas <stefankangas@gmail.com> writes:
>
>> Richard Stallman <rms@gnu.org> writes:
>>> Should we make the old name `find-file-not-found-hooks' an alias for
>>> `find-file-not-found-functions'? Perhaps make it obsolete now, and
>>> rename it in version 32?
>
>> It was declared obsolete (with `define-obsolete-variable-alias') already
>> in Emacs version 22.1, and it was subsequently removed in Emacs 29.1.
>
> Let me add some comments, as a very-long-time user.
>
> The problem I encountered has to do with auto-insert-tkld.el a package
> that dates back to 1988, and still works and does the job it was
> designed for.
When loading or compiling this file, did you encounter warnings that it
was using obsolete variables?
> Now renaming a functionality breaks down older packages (and in this
> particular case I would have preferred if that hook (or function) had
> been called find-file-not-found-hook-functions, or something like this,
> because it makes it easier for the user to pin down the problem.
>
> I recently slowed down in trying out the latest emacs versions (that is
> master), just because of this issue: renaming functions and variables will
> cause me to spend maybe a couple of days fixing things.
>
> Don't get me wrong, if there is a new exciting feature, like full BIDI
> support or prettify-symbols-mode, I will try it out.
>
> But nowadays I only upgrade if the packages I use most, like auctex and
> orgmode require it.
>
> I wished there was compatibility file, in which old for some reason
> obsolete variables, functions etc would go so that the user you upgrade
> more swiftly.
>
> Regards
>
> Uwe Brauer
--
Philip Kaludercic on peregrine
next prev parent reply other threads:[~2024-07-23 8:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-20 14:52 replacement of find-file-not-found-hooks Uwe Brauer via Emacs development discussions.
2024-07-20 15:08 ` [Solved] (was: replacement of find-file-not-found-hooks) Uwe Brauer via Emacs development discussions.
2024-07-20 15:10 ` replacement of find-file-not-found-hooks Eli Zaretskii
2024-07-20 17:37 ` Andreas Schwab
2024-07-21 15:00 ` Uwe Brauer via Emacs development discussions.
2024-07-21 15:52 ` Eli Zaretskii
2024-07-23 3:42 ` Richard Stallman
2024-07-23 4:32 ` Stefan Kangas
2024-07-23 6:52 ` Uwe Brauer
2024-07-23 8:41 ` Philip Kaludercic [this message]
2024-07-23 11:36 ` Eli Zaretskii
2024-07-23 19:34 ` Uwe Brauer
2024-07-23 20:38 ` Stefan Kangas
2024-07-24 11:13 ` Eli Zaretskii
2024-07-24 12:33 ` [toggle-read-only] (was: replacement of find-file-not-found-hooks) Uwe Brauer
2024-07-24 12:47 ` Eli Zaretskii
2024-07-24 15:50 ` [toggle-read-only] Uwe Brauer
2024-07-24 16:41 ` [toggle-read-only] Eli Zaretskii
2024-07-23 21:45 ` replacement of find-file-not-found-hooks Björn Bidar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o76ojyaf.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=oub@mat.ucm.es \
--cc=rms@gnu.org \
--cc=stefankangas@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).