From: alexhutcheson--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 45824@debbugs.gnu.org
Subject: bug#45824: 27.1; term/screen.el not loaded when TERM=screen.xterm-256color
Date: Tue, 19 Jan 2021 11:52:13 -0500 [thread overview]
Message-ID: <CACjgaUdU6pQXt9PdEEFPmzO=0GKZ9qJXE-5hV_fZLNZS2dg6eg@mail.gmail.com> (raw)
In-Reply-To: <87a6t4j4yc.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 1902 bytes --]
That behavior seems fine to me. In your example, Emacs would check
for the following, in-order:
1. linux2.6.26.el
2. linux2.6.el
3. linux2.el
This seems like the right approach - try to match minor versions, but
if there is not a config for a specific minor version, then use the
config that matches the major version.
In this specific instance, it wouldn't actually find anything, because
there is no term/linux2.el file (just a term/linux.el file). This
could be resolved by also splitting between non-numeric characters and
numbers (so we would try linux.el as a step #4), but that's not
necessary to solve my specific problem.
On Tue, Jan 19, 2021 at 10:56 AM Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Alex Hutcheson <alexhutcheson@google.com> writes:
>
> > I just checked on two of my machines (running different distributions)
> > and didn't see anything that looked like it would cause problems. Most
> > were of the form "screen.something", and a couple terminfo files
> > included dots within version specifiers (e.g. st-0.8 and st-0.7).
>
> Hm... but wouldn't that possibly cause problems? That is, if your TERM
> is
>
> linux2.6.26
>
> then if we split on dots, then Emacs will first look for
> "text/linux2.6.26.el", and then "term/linux2.6.el"... and those are
> indeed different terminfos as found on my system:
>
> linux2.6
> linux2.6.26
>
> > The command I used to list all the relevant terminfo files was:
> > find /lib/terminfo /usr/share/terminfo -name '*.*' -type f -exec
> > basename '{}' ';' | sort -u
>
> Now, there is no term/linux2.6.el, so perhaps this is irrelevant... And
> perhaps if there was a term/linux2.6.el, perhaps loading that would be
> OK in this case? Anybody got an opinion here?
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
>
--
Alex Hutcheson
alexhutcheson@google.com
[-- Attachment #2: Type: text/html, Size: 2786 bytes --]
next prev parent reply other threads:[~2021-01-19 16:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 19:04 bug#45824: 27.1; term/screen.el not loaded when TERM=screen.xterm-256color Alex Hutcheson via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-12 19:22 ` bug#45824: Alex Hutcheson via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-19 6:51 ` bug#45824: 27.1; term/screen.el not loaded when TERM=screen.xterm-256color Lars Ingebrigtsen
2021-01-19 15:34 ` alexhutcheson--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-19 15:56 ` Lars Ingebrigtsen
2021-01-19 16:52 ` alexhutcheson--- via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-01-19 18:27 ` Eli Zaretskii
2021-01-19 18:33 ` alexhutcheson--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-19 19:20 ` Eli Zaretskii
2021-01-20 16:26 ` Lars Ingebrigtsen
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='CACjgaUdU6pQXt9PdEEFPmzO=0GKZ9qJXE-5hV_fZLNZS2dg6eg@mail.gmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=45824@debbugs.gnu.org \
--cc=alexhutcheson@google.com \
--cc=larsi@gnus.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.
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.