From: Andrea Corallo via "Emacs development discussions." <emacs-devel@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: emacs-devel@gnu.org
Subject: Re: New obsolete.el file for obsolete stuff?
Date: Tue, 18 Aug 2020 12:24:18 +0000 [thread overview]
Message-ID: <xjf4kp087m5.fsf@sdf.org> (raw)
In-Reply-To: <CADwFkmm=DACoq81rDjNsm2YFnBYEAfBDFdZLqbvU9aT5J1OFOw@mail.gmail.com> (Stefan Kangas's message of "Tue, 18 Aug 2020 12:10:03 +0000")
Stefan Kangas <stefan@marxist.se> writes:
> I was investigating some XEmacs compat code the other day and stumbled
> across their library obsolete.el, which they used to put all their
> obsolete aliases.
>
> You can find their library here:
>
> https://bitbucket.org/xemacs/xemacs/src/default/lisp/obsolete.el
>
> Its Commentary says:
>
> The obsoleteness support used to be scattered throughout various
> source files. We put the stuff in one place to remove the junkiness
> from other source files and to facilitate creating/updating things
> like sysdep.el.
>
> I think this is a nice idea to basically move some cruft out of the way,
> to where we don't need to see it.
>
> Could we do something similar for Emacs? I'm thinking that we don't
> need to move all stuff at once, but if we create the file with a basic
> structure, we could start using it little by little.
Am I wrong or the trouble is that such a file would require all
necessary dependencies for the functions moved into? If that's the case
either only code with autoloaded or no dependency can be moved there or
a massive number of requires would be needed. I'm not sure the solution
is not very practical in this respect.
Regards
Andrea
--
akrl@sdf.org
next prev parent reply other threads:[~2020-08-18 12:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 12:10 New obsolete.el file for obsolete stuff? Stefan Kangas
2020-08-18 12:24 ` Andrea Corallo via Emacs development discussions. [this message]
2020-08-18 12:39 ` Stefan Kangas
2020-08-18 12:38 ` Lars Ingebrigtsen
2020-08-18 12:44 ` Stefan Kangas
2020-08-18 16:55 ` Stefan Monnier
2020-08-18 17:22 ` Eli Zaretskii
2020-08-19 14:01 ` Stefan Kangas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xjf4kp087m5.fsf@sdf.org \
--to=emacs-devel@gnu.org \
--cc=akrl@sdf.org \
--cc=stefan@marxist.se \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.