unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Marcin Kasperski <Marcin.Kasperski@mekk.waw.pl>
To: 60711@debbugs.gnu.org
Subject: bug#60711: Compose fails to generate ≤ and ≥ (only those two! and only in emacs!)
Date: Tue, 10 Jan 2023 16:13:20 +0100	[thread overview]
Message-ID: <CAJQm8RbitQ4AX=uPt6qX=b4C0dzHMb2_gL3C+N6ZER7Cu6C4ig@mail.gmail.com> (raw)

I heavily use compose sequences while writing („CapsLock - >” – and I
get nice  „→”).

Since some recent emacs update (version below):

a) I can no longer generate ≤ and ≥ in Emacs

    All combinations (Compose >=, Compose >_, Compose _>) end the same:
    - after entering Compose > there is floating window hinting ≥
    - once I type =, puff, no character in the buffer, nothing.

b) Other Compose combinations I tried work.

    In particular Compose => works in Emacs and generates ⇒,
    Compose > > makes », Compose - > makes → and so on

    (can't guarantee everything works  but from dozens of combinations
    I use I found only those two to be problematic).

c) In all other applications ≥ and ≤ are properly generated with compose
    (tried gedit, terminator, firefox, vscode …)

So, for example, pressing
      a Compose < = b Compose < < c
in gedit/code/firefox results in
      a≤b«c
while in Emacs results in
      ab«c
(and really that, I tried saving file and hex-inspecting it, no
invisible character there).


Problem appeared after some recent update (most likely after I upgraded
to emacs 28 but I am not 100% sure, could be also related to Ubuntu
upgrade).

Problem reproduces in `emacs -Q`

Version I use now:

GNU Emacs 28.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.20,
cairo version 1.16.0)
 of 2022-05-31

(Ubuntu 22.04.1 LTS,
 emacs from ppa https://launchpad.net/~kelleyk/+archive/ubuntu/emacs,
 KDE Plasma as window manager)





             reply	other threads:[~2023-01-10 15:13 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10 15:13 Marcin Kasperski [this message]
2023-01-10 15:15 ` bug#60711: Compose fails to generate ≤ and ≥ (only those two! and only in emacs!) Marcin Kasperski
2023-01-10 16:01 ` Gregory Heytings
2023-01-10 17:07   ` Eli Zaretskii
2023-01-11  7:29   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-11  8:45     ` Gregory Heytings
2023-01-11 10:21       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-11 18:45         ` Marcin Kasperski
2023-01-11 18:49           ` Marcin Kasperski
2023-01-11 18:54             ` Marcin Kasperski
2023-01-11 19:18               ` Marcin Kasperski
2023-01-11 21:15                 ` Gregory Heytings
2023-01-11 23:05                   ` Andreas Schwab
2023-01-13 14:26                   ` Marcin Kasperski
2023-01-13 14:41                     ` Marcin Kasperski
2023-01-15  0:36                       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-14 21:54                     ` Gregory Heytings
2023-01-11 21:11               ` Gregory Heytings
2023-01-11 20:01           ` Eli Zaretskii
2023-01-11 20:59           ` Gregory Heytings
2023-01-11 21:02         ` Gregory Heytings
2023-01-12  1:25           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-16  9:41             ` Gregory Heytings
2023-01-16  9:57               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-16 12:31                 ` Gregory Heytings
2023-01-17  0:41                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-09 11:01 ` 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='CAJQm8RbitQ4AX=uPt6qX=b4C0dzHMb2_gL3C+N6ZER7Cu6C4ig@mail.gmail.com' \
    --to=marcin.kasperski@mekk.waw.pl \
    --cc=60711@debbugs.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 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).