From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: tsdh@gnu.org, 48439@debbugs.gnu.org
Subject: bug#48439: 28.0.50; Support for the Alacritty terminal emulator
Date: Sat, 15 May 2021 17:00:12 +0300 [thread overview]
Message-ID: <83mtsww103.fsf@gnu.org> (raw)
In-Reply-To: <87zgwwglia.fsf@igel.home> (message from Andreas Schwab on Sat, 15 May 2021 15:43:57 +0200)
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: tsdh@gnu.org, 48439@debbugs.gnu.org
> Date: Sat, 15 May 2021 15:43:57 +0200
>
> On Mai 15 2021, Eli Zaretskii wrote:
>
> > Looks quite extensive to me. Of particular importance are: the number
> > of colors (not 256 but only 8 in alacritty), and different commands to
> > set fore- and back-ground colors.
>
> Both are overridden in the alacritty description.
OK, thanks. Then I guess Alacritty is indeed close enough to
xterm-256color. The only question I have is: does Alacritty offer any
capabilities that are not in xterm-256color? Because if it does, then
adding it to the list of aliases will prevent users from taking
advantage of those additional capabilities, because AFAIU we use the
alias without checking first whether the original terminal name has a
library. So if Alacritty has important additional features, it might
be better to prepare a separate alacritty.el file, using xterm.el as a
starting point (or even 'require'ing it).
next prev parent reply other threads:[~2021-05-15 14:00 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
2021-05-15 13:29 ` Eli Zaretskii
2021-05-15 13:43 ` Andreas Schwab
2021-05-15 14:00 ` Eli Zaretskii [this message]
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=83mtsww103.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48439@debbugs.gnu.org \
--cc=schwab@linux-m68k.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).