Re: Display of undisplayable characters: \U01F3A8 instead of diamond

[Alan Mackenzie]

Hello, Gregory.

On Fri, Aug 26, 2022 at 13:29:30 +0000, Gregory Heytings wrote:


> > A problem with this terminal emulator (along, it seems, with most 
> > others) is that it steals key sequnces which Emacs needs.

> > Amongst those which fbterm's author thought would never be used by a 
> > user are C-<space> and C-M-k.

> > Maybe fbterm has a way of freeing up these key sequences (I didn't get 
> > that far into its FAQ), but I doubt it.


> In fact the default fbterm configuration (on Debian at least) does not 
> steal those key sequences.  They are stealed only if you manually add 
> either a setuid bit or a capability on fbterm's binary.  If the setuid bit 
> or capability is set by default in other distributions, removing it should 
> be enough.  (And if you're annoyed by the warning that fbterm prints 
> because it cannot steal those key sequences, you can add a "clear" in you 
> shell startup script.)

I've tried fbterm out, thanks!  It comes up in a font which is too small
for me, but that is easily remedied in the configuration file ~/.fbterm.

Indeed it doesn't steal C-<space> or C-M-k, but it does take some other
bindings like C-<left>/C-<right>.  I don't think there's an option in
fbterm to leave all key sequences alone.

And it displays these pesky unicode punctuation characters correctly.
:-)

At the moment, I'm not sure whether I will end up using it or not.
Probably not.

-- 
Alan Mackenzie (Nuremberg, Germany).