unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 10:34:32 -0500	[thread overview]
Message-ID: <CACjgaUdmr65a6eFAbzuTWw6mzndEq03=viSMgbmovMWP5RoR9A@mail.gmail.com> (raw)
In-Reply-To: <877do9mnc0.fsf@gnus.org>

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).

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

This worked on two Debian systems (one testing, one Buster), as well
as a macOS system.


On Tue, Jan 19, 2021 at 1:51 AM Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
> Alex Hutcheson <alexhutcheson@google.com> writes:
>
> > In some common configurations, GNU Screen sets
> > TERM=screen.xterm-256color.
>
> [...]
>
> > The TERM parsing logic is documented at
> > https://www.gnu.org/software/emacs/manual/html_node/elisp/Terminal_002dSpecific.html
> > and the code is in `tty-find-type` within lisp/faces.el
> >
> > The simple fix would be to also consider periods to be a valid separator
> > within this logic.
>
> That does sound like a simple fix.  :-)  Are there any common TERM
> values that have dots in them, though?  It does seem unlikely, in which
> case this simple fix should probably work?
>
> --
> (domestic pets only, the antidote for overdose, milk.)
>    bloggy blog: http://lars.ingebrigtsen.no



-- 
Alex Hutcheson
alexhutcheson@google.com





  reply	other threads:[~2021-01-19 15:34 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 [this message]
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
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='CACjgaUdmr65a6eFAbzuTWw6mzndEq03=viSMgbmovMWP5RoR9A@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 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).