unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 56998@debbugs.gnu.org, stepnem@gmail.com
Subject: bug#56998: 29.0.50; quail input methods broken (input-method-alist empty) on master (since 261d6afd6)
Date: Fri, 05 Aug 2022 16:46:29 +0300	[thread overview]
Message-ID: <83v8r6ztu2.fsf@gnu.org> (raw)
In-Reply-To: <87fsia96ip.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri,  05 Aug 2022 15:14:38 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: stepnem@gmail.com,  56998@debbugs.gnu.org
> Date: Fri, 05 Aug 2022 15:14:38 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Is the file lisp/leim/leim-list.el being produced and exists when
> > Emacs is dumped?
> 
> Yup.  So I guess the problem is that the first build isn't loading that
> file, for some reason?

Maybe.  But how can it not load that file, when loadup.el explicitly
says to load it?

What is the contents of that file in a build where input-method-alist
is empty?

And could it be that the file is generated only after Emacs was
already built/dumped?





  reply	other threads:[~2022-08-05 13:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05  8:48 bug#56998: 29.0.50; quail input methods broken (input-method-alist empty) on master (since 261d6afd6) Štěpán Němec
2022-08-05 10:53 ` Eli Zaretskii
2022-08-05 12:14   ` Štěpán Němec
2022-08-05 12:09 ` Lars Ingebrigtsen
2022-08-05 12:18   ` Štěpán Němec
2022-08-05 12:19     ` Lars Ingebrigtsen
2022-08-05 12:22     ` Štěpán Němec
2022-08-05 12:24       ` Lars Ingebrigtsen
2022-08-05 12:29         ` Lars Ingebrigtsen
2022-08-05 12:39           ` Lars Ingebrigtsen
2022-08-05 13:11             ` Eli Zaretskii
2022-08-05 13:14               ` Lars Ingebrigtsen
2022-08-05 13:46                 ` Eli Zaretskii [this message]
2022-08-05 16:28                   ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 16:55                     ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 18:08                     ` Eli Zaretskii
2022-08-05 18:34                       ` Glenn Morris
2022-08-05 12:34         ` Štěpán Němec
2022-08-05 12:34           ` Lars Ingebrigtsen
2022-08-05 13:49           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 21:49 ` Lars Ingebrigtsen
2022-08-06 10:26   ` Štěpán Němec
2022-08-06 12:10     ` Lars Ingebrigtsen

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=83v8r6ztu2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=56998@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=stepnem@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).