all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tassilo Horn <tsdh@gnu.org>
Cc: 48439@debbugs.gnu.org
Subject: bug#48439: 28.0.50; Support for the Alacritty terminal emulator
Date: Sat, 15 May 2021 16:18:02 +0300	[thread overview]
Message-ID: <83r1i8w2yd.fsf@gnu.org> (raw)
In-Reply-To: <87v97kcigu.fsf@gnu.org> (message from Tassilo Horn on Sat, 15 May 2021 13:55:13 +0200)

> From: Tassilo Horn <tsdh@gnu.org>
> Cc: 48439@debbugs.gnu.org
> Date: Sat, 15 May 2021 13:55:13 +0200
> 
> > Is Alacritty really similar to 256-color xterm?  What are the
> > differences?
> 
> I don't know but given that it gives out itself as xterm-256color if
> terminfo doesn't know it suggests it is similar enough.

The question is how close.  If it is 90% close, then using the alias
makes sense.  But if it has enough unique features, then using an
alias will rob users of those features for no good reason.

> > Do you know where I can find the terminfo database for Alacritty?
> 
> I've attached an archive of the 3 alacritty files in my
> /usr/share/terminfo/a/ directory if that's what you were looking for.

Thanks, but these files are not recognized by 'infocmp', which I tried
to use to decompile them (assuming they were terminfo files compiled
by 'tic').

Maybe someone else will be able to tell the differences between
alacritty and xterm256color.





  reply	other threads:[~2021-05-15 13:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-15 11:07 bug#48439: 28.0.50; Support for the Alacritty terminal emulator Tassilo Horn
2021-05-15 11:30 ` Eli Zaretskii
2021-05-15 11:55   ` Tassilo Horn
2021-05-15 13:18     ` Eli Zaretskii [this message]
2021-05-15 13:29       ` Eli Zaretskii
2021-05-15 13:43         ` Andreas Schwab
2021-05-15 14:00           ` Eli Zaretskii
2021-05-25 20:40             ` 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=83r1i8w2yd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=48439@debbugs.gnu.org \
    --cc=tsdh@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.
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.