unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Marshall <robert@capuchin.co.uk>
To: Po Lu <luangruo@yahoo.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 58135@debbugs.gnu.org
Subject: bug#58135: 29.0.50; Typing getting garbled in mail-mode
Date: Wed, 7 Dec 2022 19:17:16 +0000	[thread overview]
Message-ID: <25488.59068.866352.235693@capuchin.co.uk> (raw)
In-Reply-To: <87fsev7ybp.fsf@yahoo.com>

Po Lu writes:
 > Eli Zaretskii <eliz@gnu.org> writes:
 > 
 > >> Date: Mon, 7 Nov 2022 11:08:59 +0000
 > >> From: Robert Marshall <robert@capuchin.co.uk>
 > >> Cc: luangruo@yahoo.com,
 > >>     58135@debbugs.gnu.org
 > >> 
 > >> 
 > >> Eli Zaretskii writes:
 > >>  > Is the wrong order real, or just on display?  IOW, what happens if you
 > >>  > save the buffer to a file -- do you see the wrong order in the file as
 > >>  > well?
 > >>  > 
 > >> 
 > >> I saved a buffer containing garbled "r dehsangul ce" - I typed "rules
 > >> changed" to a file and the contents of the file were as in the buffer
 > >> - so the wrong order was real rather than just being displayed.
 > >
 > > That would mean something really changes the input events that Emacs
 > > receives.  Does "C-h l" after this happens indeed shows the characters
 > > in the wrong order?
 > 
 > And if it does, would you please try turning off input method support,
 > by running Emacs like so:
 > 
 >   emacs (other options here) -xrm 'Emacs.useXIM: off'
 > 
 > the extra layers of indirection involved in ferrying events to and fro
 > the input method may be causing this problem, and narrowing it down to
 > the input method would make it easier to debug.

I've run emacs with those options for 2+ weeks now and am yet to
see the problem occurring, so that appears to avoid the problem.

Robert





  parent reply	other threads:[~2022-12-07 19:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28  9:01 bug#58135: 29.0.50; Typing getting garbled in mail-mode Robert Marshall
2022-09-28 12:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-01 15:44   ` Robert Marshall
2022-11-01 18:00     ` Eli Zaretskii
2022-11-07 11:08       ` Robert Marshall
2022-11-07 12:14         ` Eli Zaretskii
2022-11-07 12:18           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-07 18:27             ` Robert Marshall
2022-12-07 19:17             ` Robert Marshall [this message]
2022-12-08  0:49               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-08 12:35                 ` Robert Marshall
2022-12-08 12:53                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-08 13:34                     ` Robert Marshall
2022-12-09  1:06                       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-14 11:36                         ` Robert Marshall
2022-12-14 13:28                           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-29 11:08 ` Lars Ingebrigtsen
2022-09-29 11:44   ` Robert Marshall

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=25488.59068.866352.235693@capuchin.co.uk \
    --to=robert@capuchin.co.uk \
    --cc=58135@debbugs.gnu.org \
    --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).