all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: emacs-devel@gnu.org
Subject: Using Emacs in fbterm.
Date: Mon, 29 Aug 2022 16:41:00 +0000	[thread overview]
Message-ID: <YwzsHA9ctqFVmRTj@ACM> (raw)

Hello, Emacs.

I think it's time to begin a new thread on fbterm, which isn't about
undisplayable characters any more.

Just as a matter of interest, I've amended my copy of the fbterm's
source code so as to remove most of the "stolen" key combinations,
leaving just S-<prior> and S-<next> in place.  These scroll the screen
vertically, allowing one to view previous messages or commands.

fbterm is hosted at GitHub, where there seem to be 28 forks of it, most
of them, probably, being very slight differences from their forkees (is
that a word?).  So much for free software.  ;-)

In the GNU/Linux distribution I use, Gentoo, the version of fbterm is
one of those forks.  One change in it, made 7 years ago, was changing
the setting of the environment variable TERM from "linux" to "fbterm".
It seems that this will vary randomly between these forks, and also
randomly between G/L distributions.  There might be something in the
terminfo setup to enable one to distinguish fbterm from the Linux
console when TERM is "linux".

There is a problem with colours in Emacs in fbterm.  When one does M-:
(defined-colors) it prints a list of just eight colours, black, red,
...., white.

However, the face constructing mechanism seems to assume more than eight
colours, and this seems buggy.  The face hi-green, for example, rather
than having background "green" gets "light green".  This appears on the
terminal as dark yellow, which is clearly wrong.

Also the face mode-line-inactive is indistinguishable from the default
face, so when there're more than one window in the frame, they are less
easy to distinguish than they should be.

-- 
Alan Mackenzie (Nuremberg, Germany).



             reply	other threads:[~2022-08-29 16:41 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29 16:41 Alan Mackenzie [this message]
2022-08-29 17:33 ` Using Emacs in fbterm 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
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=YwzsHA9ctqFVmRTj@ACM \
    --to=acm@muc.de \
    --cc=emacs-devel@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.