all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Carmen Bianca Bakker <carmen@carmenbianca.eu>
Cc: 30092@debbugs.gnu.org
Subject: bug#30092: Compose key behaviour is incorrect when locale is set to Esperanto
Date: Thu, 04 Feb 2021 14:45:50 +0100	[thread overview]
Message-ID: <87r1lwq73l.fsf@gnus.org> (raw)
In-Reply-To: <f7ae3bf0-165e-17ac-fa2b-15231d5c05b9@carmenbianca.eu> (Carmen Bianca Bakker's message of "Fri, 12 Jan 2018 22:15:17 +0100")

Carmen Bianca Bakker <carmen@carmenbianca.eu> writes:

> I am running into an unusual bug of sorts.  That is: The behaviour of
> the compose key is incorrect when the locale is set to "eo"
> (Esperanto).  The exact behaviour is as follows:
>
> - When running `XMODIFIERS="" emacs`, `<MULTI_KEY> a e` does not produce æ.  It
>   simply produces nothing.  `<MULTI_KEY> ' e` correctly produces é, however.

(I'm going through old bug reports that unfortunately got no response at
the time.)

This bug is still present in Emacs 28 -- I reproduced it with

XMODIFIERS="" LC_ALL=eo ./src/emacs -Q

(after defining the "eo" locale on this laptop).

Before I go poking into this any further -- has anybody else here on the
mailing list encountered this problem before?

> - When running `XMODIFIERS=@im=ibus emacs` (my default), simply pressing the
>   compose key results in `<MULTI_KEY> is undefined`.

This doesn't seem to happen any more, though.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2021-02-04 13:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-12 21:15 bug#30092: Compose key behaviour is incorrect when locale is set to Esperanto Carmen Bianca Bakker
2021-02-04 13:45 ` Lars Ingebrigtsen [this message]

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=87r1lwq73l.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=30092@debbugs.gnu.org \
    --cc=carmen@carmenbianca.eu \
    /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.