all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 48439@debbugs.gnu.org, Andreas Schwab <schwab@linux-m68k.org>,
	tsdh@gnu.org
Subject: bug#48439: 28.0.50; Support for the Alacritty terminal emulator
Date: Tue, 25 May 2021 22:40:15 +0200	[thread overview]
Message-ID: <871r9ucztc.fsf@gnus.org> (raw)
In-Reply-To: <83mtsww103.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 15 May 2021 17:00:12 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> OK, thanks.  Then I guess Alacritty is indeed close enough to
> xterm-256color.

Since it's close enough, I've now applied Tassilo's patch.

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

That's true -- but I guess we'll just have to wait and see whether
there's any request for supporting these additional features (if any).
If there is, removing the alias is easy enough.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2021-05-25 20:40 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
2021-05-25 20:40             ` Lars Ingebrigtsen [this message]

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=871r9ucztc.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=48439@debbugs.gnu.org \
    --cc=eliz@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 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.