unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: acm@muc.de, schwab@linux-m68k.org, emacs-devel@gnu.org
Subject: Re: Using Emacs in fbterm.
Date: Tue, 30 Aug 2022 15:10:55 +0300	[thread overview]
Message-ID: <83czciue28.fsf@gnu.org> (raw)
In-Reply-To: <dacea9288826293cc416@heytings.org> (message from Gregory Heytings on Tue, 30 Aug 2022 12:04:24 +0000)

> Date: Tue, 30 Aug 2022 12:04:24 +0000
> From: Gregory Heytings <gregory@heytings.org>
> cc: acm@muc.de, schwab@linux-m68k.org, emacs-devel@gnu.org
> 
> > But since fbterm doesn't always announce itself as such, but instead 
> > calls itself "linux", this is not reliable enough, is it?
> 
> It is.  There are two cases: if it calls itself "linux", you get eight 
> colors, and everything works as expected with those eight colors.  If it 
> calls itself "fbterm", you get wrong colors (without the patch).
>
> (And of course we can also tell users to set TERM=fbterm in the FAQ 
> entry.)

Maybe it's worth telling this in a comment in fbterm.el?  I mean that
if the user's fbterm doesn't identify itself as such, they will get
only 8 colors, unless they fiddle with the environment.

> >> And how can I check whether compositions should be disabled, that is, 
> >> if they confuse cursor movement?
> >
> > There are some compositions in HELLO, and you can also try some long 
> > Emoji sequences.
> >
> 
> As far as I can tell, cursor movement works as expected with 
> auto-composition-mode t.
> 
> So I suggest the following patch, with an additional note in the FAQ 
> entry.

Thanks, this is fine by me.



  reply	other threads:[~2022-08-30 12:10 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
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 [this message]
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

  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=83czciue28.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --cc=gregory@heytings.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 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).