unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: yantar92@posteo.net, kyle@kyleam.com, stefankangas@gmail.com,
	emacs-devel@gnu.org
Subject: Re: master 5a125fb5a97 1/2: Update to Org 9.7.3
Date: Wed, 12 Jun 2024 19:50:22 +0300	[thread overview]
Message-ID: <86wmmuyuk1.fsf@gnu.org> (raw)
In-Reply-To: <jwvv82edxzk.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Wed, 12 Jun 2024 10:46:07 -0400)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Ihor Radchenko <yantar92@posteo.net>,  kyle@kyleam.com,
>   stefankangas@gmail.com,  emacs-devel@gnu.org
> Date: Wed, 12 Jun 2024 10:46:07 -0400
> 
> >> The existence of such script implies that .texi files generated by Org
> >> are not well-formatted. May you please explain why org.org file needs to
> >> be parsed and why parsing org.texi is not sufficient?
> > I don't think it has anything to do with formatting of org.texi.  The
> > issue here is that info/DIR file might be generated when org.texi is
> > not yet available or not yet up-to-date, such as during bootstrap or
> > after some change in org.org.  IOW, the reason for this behavior is
> > that we want to produce info/DIR from the source files, not from the
> > generated files.
> 
> I don't think this argument is very convincing: getting the info "from
> org.org via an awk script" is not that different from getting it "from
> org.org via org-export plus install-info".

If we could use install-info, we didn't need that script at all.  The
comments in the top-level Makefile explain why we don't use
install-info for generating DIR in the build tree.



  reply	other threads:[~2024-06-12 16:50 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <171796793548.23337.12512115872160390161@vcs2.savannah.gnu.org>
     [not found] ` <20240609211858.A2C31C1F9FB@vcs2.savannah.gnu.org>
2024-06-10  0:40   ` master 5a125fb5a97 1/2: Update to Org 9.7.3 Po Lu
2024-06-10  1:14     ` Kyle Meyer
2024-06-10  3:45       ` Po Lu
2024-06-10  3:58         ` Po Lu
2024-06-12 13:08         ` Ihor Radchenko
2024-06-12 13:13           ` Eli Zaretskii
2024-06-12 13:23             ` Ihor Radchenko
2024-06-12 13:30               ` Eli Zaretskii
2024-06-14 13:18                 ` Ihor Radchenko
2024-06-10 11:13       ` Eli Zaretskii
2024-06-11 10:05         ` Ihor Radchenko
2024-06-11 12:23           ` Eli Zaretskii
2024-06-11 13:10             ` Robert Pluim
2024-06-14  9:49               ` Ihor Radchenko
2024-06-14 11:39                 ` Eli Zaretskii
2024-06-14 12:02                   ` Robert Pluim
2024-06-11 13:16             ` Stefan Monnier
2024-06-12 13:49               ` Ihor Radchenko
2024-06-12 14:41                 ` Stefan Monnier
2024-06-13 13:00             ` Ihor Radchenko
2024-06-13 13:43               ` Eli Zaretskii
2024-06-13 14:34                 ` Stefan Monnier
2024-06-14 12:39                 ` Ihor Radchenko
2024-06-13 13:32             ` Ihor Radchenko
2024-06-13 13:54               ` Eli Zaretskii
2024-06-15 11:20                 ` Ihor Radchenko
2024-06-15 12:46                   ` Eli Zaretskii
2024-06-15 12:55                     ` Syncing Org bugfix releases with emacs-30 branch (was: master 5a125fb5a97 1/2: Update to Org 9.7.3) Ihor Radchenko
2024-06-15 13:02                       ` Eli Zaretskii
2024-06-16 11:09                         ` Ihor Radchenko
2024-06-15 16:58                     ` master 5a125fb5a97 1/2: Update to Org 9.7.3 Kyle Meyer
2024-06-11 11:03   ` Stefan Kangas
2024-06-12  3:45     ` Kyle Meyer
2024-06-12  8:52       ` Eli Zaretskii
2024-06-12 12:58         ` Ihor Radchenko
2024-06-12 13:02           ` Eli Zaretskii
2024-06-12 13:21             ` Ihor Radchenko
2024-06-12 13:29               ` Eli Zaretskii
2024-06-12 14:14                 ` Stefan Kangas
2024-06-13 16:12                   ` Ihor Radchenko
2024-06-13 16:48                     ` Eli Zaretskii
2024-06-12 14:46             ` Stefan Monnier
2024-06-12 16:50               ` Eli Zaretskii [this message]
2024-06-13 15:44                 ` Ihor Radchenko
2024-06-13 15:55                   ` Eli Zaretskii

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=86wmmuyuk1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=kyle@kyleam.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=stefankangas@gmail.com \
    --cc=yantar92@posteo.net \
    /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).