Your message dated Mon, 13 Nov 2023 01:34:17 +0530
with message-id <20231112200417.tcbqjewpvus2h...@office.mailbox.org>
and subject line Re: Bug#908226: Unicode input does not actually input the
selected symbol
has caused the Debian Bug report #908226,
regarding Unicode input does not actually input the selected symbol
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
908226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908226
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kitty
Version: 0.11.3-1
Severity: normal
Tags: upstream
I can bring up the unicode input overlay with C-S-u, but no matter what symbol I
select there, once I press Enter to input it, nothing happens, no symbol appears
in my terminal. My kitty configuration consists of color settings only, no font
configured. I tried with symbols that otherwise work, like 67 ('g'), but that
does not seem to have any effect at all either. Kitty does not log an error,
either, as far as I see.
I tried with different programs running in the terminal, but that did not help
either: whether I used zsh, bash, or even cat, no symbol was input.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages kitty depends on:
ii kitty-terminfo 0.11.3-1
ii libc6 2.27-5
ii libfontconfig1 2.13.0-5
ii libfreetype6 2.8.1-2
ii libharfbuzz0b 1.8.8-2
ii libpng16-16 1.6.34-2
ii libpython3.6 3.6.6-1
ii libx11-6 2:1.6.6-1
ii libx11-xcb1 2:1.6.6-1
ii libxkbcommon-x11-0 0.8.2-1
ii libxkbcommon0 0.8.2-1
ii python3 3.6.5-3
ii python3.6 3.6.6-1
ii zlib1g 1:1.2.11.dfsg-1
Versions of packages kitty recommends:
pn kitty-doc <none>
kitty suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Since this is resolved a long time back, I am closing it.
On Sun, 07 Oct 2018 00:31:53 +0200 Gergely Nagy <ge...@csillger.hu> wrote:
> An additional data point: I upgraded to the latest Kitty in testing
> today, and noticed a thing in the changelog:
>
> + Add support for IME via IBus, enabled by setting GLFW_IM_MODULE=ibus
>
> So I exported that variable before starting kitty, and inputting unicode
> works now. It does not pop up the symbol selection kitten, but lets me
> enter the code (which is perfect, this is the same behaviour
> gnome-terminal has).
>
> As far as I'm concerned, this issue can be closed.
>
> --
> |8]
signature.asc
Description: PGP signature
--- End Message ---
