unofficial mirror of bug-gnu-emacs@gnu.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 14:30:40 +0300	[thread overview]
Message-ID: <83y2cgw7xb.fsf@gnu.org> (raw)
In-Reply-To: <87y2cgcki3.fsf@gnu.org> (message from Tassilo Horn on Sat, 15 May 2021 13:07:59 +0200)

> From: Tassilo Horn <tsdh@gnu.org>
> Date: Sat, 15 May 2021 13:07:59 +0200
> 
> So I can either set TERM=xterm-256color in my Alacritty config or use
> the following patch to alias alacritty to xterm in Emacs.
> 
> --8<---------------cut here---------------start------------->8---
> 1 file changed, 1 insertion(+), 1 deletion(-)
> lisp/faces.el | 2 +-
> 
> modified   lisp/faces.el
> @@ -46,7 +46,7 @@ term-file-aliases
>      ("vt320" . "vt200")
>      ("vt400" . "vt200")
>      ("vt420" . "vt200")
> -    )
> +    ("alacritty" . "xterm"))
>    "Alist of terminal type aliases.
>  Entries are of the form (TYPE . ALIAS), where both elements are strings.
>  This means to treat a terminal of type TYPE as if it were of type ALIAS."
> --8<---------------cut here---------------end--------------->8---
> 
> IMHO, it would make sense to have that alias is place at least until
> someone comes up with "proper" support for Alacritty.

Is Alacritty really similar to 256-color xterm?  What are the
differences?  Do you know where I can find the terminfo database for
Alacritty?





  reply	other threads:[~2021-05-15 11:30 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 [this message]
2021-05-15 11:55   ` Tassilo Horn
2021-05-15 13:18     ` Eli Zaretskii
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

  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=83y2cgw7xb.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 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).