unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Christian Brolin <cbrolin@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 64300@debbugs.gnu.org
Subject: bug#64300: 28.2; Can no longer input some tokens.
Date: Thu, 06 Jul 2023 19:50:33 +0800	[thread overview]
Message-ID: <87leftl0mu.fsf@yahoo.com> (raw)
In-Reply-To: <b4774b15-0892-c247-900f-ca276b863a2b@gmail.com> (Christian Brolin's message of "Thu, 6 Jul 2023 10:17:22 +0200")

Christian Brolin <cbrolin@gmail.com> writes:

> Hi, sorry for late reply.
>
> I'm currently using:
> GNU Emacs 28.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.37,
> cairo version 1.16.0)
>  of 2023-03-16, modified by Debian
>
> I don't know how to find out my previous version, but since I accept
> updates regularly, I guess it was the latest Debian build before Jun
> 26.

Thanks.  Then I guess it's unrelated to the misguided attempts to
work-around a bug in the Xlib XIM implementation that were installed in
Emacs 28.

> The problem still persist, but now I found out, only when I start
> Emacs from the main menu, not when I start it from a terminal, so
> maybe some problem with the environment. I tried to add LANG=C.UTF-8
> to the menu entry which helped! So this is no longer an issue for
> me. But I still get the gray Pop-up somewhere on the screen when I
> press a modifier, e.g. ~ until I press the second key. I don't
> remember to have seen this before, is this a new feature? And if so,
> maybe it is related to this issue. But the important thing is that I
> now can use Emacs again.

Xlib needs the system locale to be correctly defined in order to
negotiate text encodings with the input method.  Emacs also needs to see
a valid `locale-coding-system' in order to decode keyboard input.

In order to rule out any chance of this being a bug in Emacs, would you
please reply with the values of the environment variables $XMODIFIERS,
$LANG, and that of `locale-coding-system', in an Emacs session run
without any modifications to the menu entry?

TIA.





  reply	other threads:[~2023-07-06 11:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26  7:30 bug#64300: 28.2; Can no longer input some tokens Christian Brolin
2023-07-01  8:37 ` Eli Zaretskii
2023-07-01  9:41   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-06  7:12     ` Eli Zaretskii
2023-07-06  8:17       ` Christian Brolin
2023-07-06 11:50         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-07-06 16:37           ` Christian Brolin
2023-07-06 16:41           ` Christian Brolin
2023-07-07  0:43             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-07  5:35               ` Eli Zaretskii

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=87leftl0mu.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=64300@debbugs.gnu.org \
    --cc=cbrolin@gmail.com \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.com \
    /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).