From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: larsi@gnus.org, jonas@bernoul.li, p.stephani2@gmail.com,
53316@debbugs.gnu.org
Subject: bug#53316: 28.0.91; Missing Transient manual in Emacs
Date: Thu, 17 Feb 2022 08:23:40 +0200 [thread overview]
Message-ID: <83r182105v.fsf@gnu.org> (raw)
In-Reply-To: <6ar182selo.fsf@fencepost.gnu.org> (message from Glenn Morris on Wed, 16 Feb 2022 16:09:39 -0500)
> From: Glenn Morris <rgm@gnu.org>
> Date: Wed, 16 Feb 2022 16:09:39 -0500
> Cc: Lars Ingebrigtsen <larsi@gnus.org>,
> Philipp Stephani <p.stephani2@gmail.com>, 53316@debbugs.gnu.org
>
> > And I don't think it makes sense to add the org file if some of the
> > code needed to produce the texi file are not available inside Emacs.
> > Eli would just have had to fix many more issues manually.
>
> Then IMO this manual should not be distributed with Emacs, until such
> time as the required build machinery can be.
That's IMNSHO an extremist POV with which I cannot disagree more.
It's tantamount to saying that if we have a bug in Emacs, we cannot
make a release until we fix it.
As long as we are working on this issue, and intend to eventually
provide the Org source in the distribution, I see no reason to remove
the manual from the distribution. The Texinfo source will be in the
tarball, can be used to make changes in the manual, and after my
extensive changes one can no longer say that Texinfo is not the real
source anyway.
We should strive to fix the issues with generating the manual from Org
on master, before Emacs 29 is released. Jonas, if you need any help
with that, please holler.
next prev parent reply other threads:[~2022-02-17 6:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 13:07 bug#53316: 28.0.91; Missing Transient manual in Emacs Philipp Stephani
2022-01-21 11:29 ` Lars Ingebrigtsen
2022-01-25 20:30 ` Jonas Bernoulli
2022-01-25 20:41 ` Philipp Stephani
2022-01-25 21:15 ` Jonas Bernoulli
2022-02-15 16:57 ` Jonas Bernoulli
2022-01-26 9:08 ` Michael Albinus
2022-02-15 16:53 ` Jonas Bernoulli
2022-02-15 19:09 ` Eli Zaretskii
2022-02-15 21:39 ` Jonas Bernoulli
2022-02-16 3:25 ` Eli Zaretskii
2022-02-15 20:17 ` Glenn Morris
2022-02-15 21:46 ` Jonas Bernoulli
2022-02-16 21:09 ` Glenn Morris
2022-02-17 6:23 ` Eli Zaretskii [this message]
2022-02-19 4:57 ` Richard Stallman
2022-02-19 8:46 ` Eli Zaretskii
2022-02-21 4:34 ` Richard Stallman
2022-02-21 5:47 ` Eli Zaretskii
2022-02-23 6:45 ` Richard Stallman
2022-02-23 12:18 ` Jonas Bernoulli
2022-02-25 5:00 ` Richard Stallman
2022-02-23 12:45 ` Eli Zaretskii
2022-02-19 9:27 ` Glenn Morris
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=83r182105v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53316@debbugs.gnu.org \
--cc=jonas@bernoul.li \
--cc=larsi@gnus.org \
--cc=p.stephani2@gmail.com \
--cc=rgm@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 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).