unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 45824@debbugs.gnu.org, alexhutcheson@google.com
Subject: bug#45824: 27.1; term/screen.el not loaded when TERM=screen.xterm-256color
Date: Tue, 19 Jan 2021 20:27:43 +0200	[thread overview]
Message-ID: <83y2go7peo.fsf@gnu.org> (raw)
In-Reply-To: <87a6t4j4yc.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue,  19 Jan 2021 16:56:27 +0100)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Tue, 19 Jan 2021 16:56:27 +0100
> Cc: 45824@debbugs.gnu.org
> 
> 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?

Maybe we should just introduce a way for users to specify the terminal
type that would override the value of TERM in the environment?  Some
defcustom that could be set in the init file?  That way, we don't need
to worry about inventing a new rule, with all the unintended
consequences that could bring us.





  parent reply	other threads:[~2021-01-19 18:27 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
2021-01-19 18:27       ` Eli Zaretskii [this message]
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

  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=83y2go7peo.fsf@gnu.org \
    --to=eliz@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 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).