all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: OKURI-NASI
Date: Mon, 30 May 2022 11:47:47 +0200	[thread overview]
Message-ID: <87ilpnxsfw.fsf@gnus.org> (raw)
In-Reply-To: <83mtezkb3r.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 30 May 2022 05:28:24 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> I don't know if we need it that early.  The only way to know is to
> try.  We seem to need it before loaddefs.el is generated, at least.

Do we need the ja-dic.el file before loaddefs.el?  We need leim-list.el,
I think, and leim/Makefile generates both of those files, so I think if
we just decouple those things, then we move the ja-dic.el compilation
later.

But the dependencies here aren't quite clear, and I may be misreading
the code and makefiles here.

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



  reply	other threads:[~2022-05-30  9:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-29 20:18 OKURI-NASI Lars Ingebrigtsen
2022-05-29 20:22 ` OKURI-NASI Lars Ingebrigtsen
2022-05-30  2:28   ` OKURI-NASI Eli Zaretskii
2022-05-30  9:47     ` Lars Ingebrigtsen [this message]
2022-05-30 11:39       ` OKURI-NASI Eli Zaretskii
2022-05-30 11:44         ` OKURI-NASI Lars Ingebrigtsen
2022-05-30 11:49           ` OKURI-NASI Lars Ingebrigtsen
2022-05-30 12:08           ` OKURI-NASI Eli Zaretskii
2022-05-30 15:22             ` OKURI-NASI Lars Ingebrigtsen
2022-06-01  2:54               ` OKURI-NASI Lars Ingebrigtsen
2022-05-30  7:31 ` OKURI-NASI Stefan Kangas
2022-05-30  9:53   ` OKURI-NASI Lars Ingebrigtsen
2022-05-30 13:06     ` OKURI-NASI Stefan Monnier
2022-05-30 13:19       ` OKURI-NASI 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ilpnxsfw.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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.