From: Gregory Heytings <gregory@heytings.org>
To: Alan Mackenzie <acm@muc.de>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: Using Emacs in fbterm.
Date: Mon, 29 Aug 2022 20:52:48 +0000 [thread overview]
Message-ID: <a77ca586b6d5af3200f6@heytings.org> (raw)
In-Reply-To: <Yw0jFLNAcBHeizZF@ACM>
>
> Why should Emacs need adapting? Surely these terminfo entries for
> fbterm's private colours should suffice for ncurses to display them
> correctly. Or am I missing something?
>
I meant that (IIUC) an additional file should be added in lisp/term/ for
fbterm, not that Emacs should itself send these escape sequences. See the
comment in lisp/term/tty-colors.el.
next prev parent reply other threads:[~2022-08-29 20:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 16:41 Using Emacs in fbterm Alan Mackenzie
2022-08-29 17:33 ` Eli Zaretskii
2022-08-29 18:44 ` Alan Mackenzie
2022-08-29 18:53 ` Eli Zaretskii
2022-08-29 18:54 ` Gregory Heytings
2022-08-29 18:59 ` Eli Zaretskii
2022-08-29 19:29 ` Gregory Heytings
2022-08-29 19:42 ` Eli Zaretskii
2022-08-29 19:45 ` Gregory Heytings
2022-08-29 19:55 ` Gregory Heytings
2022-08-29 19:34 ` Andreas Schwab
2022-08-29 19:43 ` Gregory Heytings
2022-08-29 19:52 ` Andreas Schwab
2022-08-29 20:27 ` Gregory Heytings
2022-08-29 20:35 ` Alan Mackenzie
2022-08-29 20:52 ` Gregory Heytings [this message]
2022-08-29 22:28 ` Gregory Heytings
2022-08-30 11:32 ` Eli Zaretskii
2022-08-30 12:04 ` Gregory Heytings
2022-08-30 12:10 ` Eli Zaretskii
2022-08-30 21:10 ` Gregory Heytings
2022-08-30 13:16 ` Stefan Monnier
2022-08-30 15:37 ` Gregory Heytings
2022-08-30 18:26 ` Stefan Monnier
2022-08-30 21:20 ` Gregory Heytings
2022-08-30 21:56 ` Stefan Monnier
2022-08-30 22:07 ` Gregory Heytings
2022-09-04 2:59 ` Stefan Monnier
2022-08-29 18:50 ` Gregory Heytings
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=a77ca586b6d5af3200f6@heytings.org \
--to=gregory@heytings.org \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.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.