From: Richard Wordingham <richard.wordingham@ntlworld.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Help for tpu-edt Legacy Users
Date: Sun, 20 Feb 2022 15:28:53 +0000 [thread overview]
Message-ID: <20220220152853.75974a24@JRWUBU2> (raw)
In-Reply-To: <834k4tya18.fsf@gnu.org>
On Sun, 20 Feb 2022 14:53:07 +0200
Eli Zaretskii <eliz@gnu.org> wrote:
> > 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.
Ah, I misinterpreted the problem in my .tpu-keys, a file tpu-edt users
are commanded to create on first use. The problem was that the line
(define-obsolete-variable-alias 'GOLD-map 'tpu-gold-map "23.1")
had been deleted from tpu-edt.el since 26.3. The file .tpu-keys makes
frequent reference to it. Mine's picked up a lot of tweaks over the
years to make it work on VT100, Sun and Windows keyboards for directly
connected terminals and X-servers. I've therefore given it the guarded
work-around
(if (and (functionp 'version<=) (version<= "28.0.91" emacs-version))
(define-obsolete-variable-alias 'GOLD-map 'tpu-gold-map "23.1"))
I need it to work as far back as Emacs 20.2, which I thinks predates
the function version<=. I'd really like it just to check for GOLD-map
not being defined as a variable, but I couldn't find the syntax for
that.
Richard.
next prev parent reply other threads:[~2022-02-20 15:28 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
2022-02-20 15:28 ` Richard Wordingham [this message]
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=20220220152853.75974a24@JRWUBU2 \
--to=richard.wordingham@ntlworld.com \
--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).