From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Help for tpu-edt Legacy Users
Date: Sun, 20 Feb 2022 14:53:07 +0200 [thread overview]
Message-ID: <834k4tya18.fsf@gnu.org> (raw)
In-Reply-To: <20220220113452.781a1145@JRWUBU2> (message from Richard Wordingham on Sun, 20 Feb 2022 11:34:52 +0000)
> Date: Sun, 20 Feb 2022 11:34:52 +0000
> From: Richard Wordingham <richard.wordingham@ntlworld.com>
>
> For a legacy user who has been happily using the TPU-EDT key bindings,
> buffers and replacement commands for decades, where should I put the
> now removed tpu-edt and tpu-extras packages? (There are three files -
> tpu-mapper.el is not to be forgotten.) Should they just go in
> directory site-lisp, or maybe lisp/obsolete? I've currently put
> the versions from Emacs 26.3 in ~/.emacs.d/obsolete, and tpu-edt.el (the
> only one I've been using) is so far working fine in Emacs 28.0.91. I'm
> currently explicitly loading (function load) them, as I had been for
> previous versions of Emacs.
These files were not removed yet, they are in lisp/obsolete.
next prev parent reply other threads:[~2022-02-20 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 11:34 Help for tpu-edt Legacy Users Richard Wordingham
2022-02-20 12:53 ` Eli Zaretskii [this message]
2022-02-20 15:28 ` Richard Wordingham
2022-02-20 15:42 ` Eli Zaretskii
2022-02-20 20:30 ` Richard Wordingham
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=834k4tya18.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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.
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).