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

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Sun, 29 May 2022 22:22:25 +0200
> 
> Lars Ingebrigtsen <larsi@gnus.org> writes:
> 
> > Because it's a bit annoying (especially since make isn't doing much else
> > while parsing/generating the dictionary).
> 
> Or perhaps we could just move generating that file until after we've
> dumped Emacs for the final time?  It would make things more parallel,
> and we don't need ja-dic.el before we dump?  Or do we?

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.



  reply	other threads:[~2022-05-30  2:28 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   ` Eli Zaretskii [this message]
2022-05-30  9:47     ` OKURI-NASI Lars Ingebrigtsen
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=83mtezkb3r.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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.