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: Eli Zaretskii <eliz@gnu.org>
Cc: 64805@debbugs.gnu.org, YOSHINO Yoshihito <yy.y.ja.jp@gmail.com>
Subject: bug#64805: 28.2; XIM cursor position is incorrect
Date: Mon, 24 Jul 2023 20:05:24 +0800	[thread overview]
Message-ID: <87sf9d1pmj.fsf@yahoo.com> (raw)
In-Reply-To: <835y69tw3s.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 24 Jul 2023 13:57:59 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: YOSHINO Yoshihito <yy.y.ja.jp@gmail.com>
>> Date: Sun, 23 Jul 2023 19:17:19 +0900
>> 
>> I use Debian in Japanese and `uim' for an XIM server,
>> which is a default in Debian Japanese desktop.
>> 
>> Recently I have upgraded Debian to its new stable version,
>> and subsequently upgraded Emacs from 27.1 to 28.2.
>> 
>> On Emacs 27.1, cursor position reported via XIM is the same as those in
>> the current buffer, and uim displays its input candidate window adjacent
>> to the position, as found in the attached screenshot `27.1.png'.
>> This is the expected behavior.
>> 
>> On Emacs 28.2, however, the cursor position is far below and outside the
>> Emacs frame, as found in the attached screenshot `28.2.png'.
>> 
>> I have bisected Emacs git repository between 27.1 and 28.2, and found
>> that this regression has been caused by commit
>> 2a64de5e982fb8b868b76626ac2e92ddfafc9ca5, which was introduced in the
>> following bug report:
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=10867
>> 
>> Reverting the commit restores the expected behavior.
>
> Maybe we should have a Lisp variable to control whether that change is
> in effect.
>
> Po Lu, any other ideas?  Perhaps this is already fixed in Emacs 29?
>
> Thanks.

I think I already fixed this in time for Emacs 29, but to avoid
disruptions for users of input methods that are affected by the Xlib bug
that was the subject of #10867 (approximately 75% of CJK X desktop
users), the fix is located behind an X resource.

Yoshihito-san probably needs to place:

  Emacs.inputStyle: overthespot

in his .Xresources or .Xdefaults.





  reply	other threads:[~2023-07-24 12:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-23 10:17 bug#64805: 28.2; XIM cursor position is incorrect YOSHINO Yoshihito
2023-07-24 10:57 ` Eli Zaretskii
2023-07-24 12:05   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-08-03  7:59     ` Eli Zaretskii
2023-08-03  8:36       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-03  9:05         ` Eli Zaretskii
2023-08-03  9:15           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87sf9d1pmj.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=64805@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=yy.y.ja.jp@gmail.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).