From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Andrew Tropin <andrew@trop.in>
Cc: 57280@debbugs.gnu.org
Subject: [bug#57280] [PATCH 0/3] Add documentation-files argument to emacs build system.
Date: Fri, 19 Aug 2022 17:39:51 +0200 [thread overview]
Message-ID: <c76deb583d7ef2d9ecaa173c3c1cdf0a9280aa84.camel@gmail.com> (raw)
In-Reply-To: <87wnb47nz9.fsf@trop.in>
Am Freitag, dem 19.08.2022 um 09:21 +0300 schrieb Andrew Tropin:
> On 2022-08-19 06:19, Liliana Marie Prikler wrote:
> > I think it's possible to cover most of those with heuristics. For
> > the rest, we can still override the phase or just rename the file
> > to something our heuristics handle.
> >
>
> If there is an info file(s) do nothing.
> If there are texinfo file build them.
> If there are no texinfo files build README.org or README.
>
> Something like that?
>
> Will play around with it a little bit and will publish v2 next week.
I'd word those in terms of for-each, i.e. "build all texinfo files and
org-mode files". Don't trust already compiled sources, i.e. if there's
both README.info and README.org, you still want to generate README.info
from README.org (though "README" doesn't sound like a particular good
heuristic for an org-file to makeinfo from).
> > >
Cheers
next prev parent reply other threads:[~2022-08-19 15:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wnb5lhyr.fsf@trop.in>
[not found] ` <107d9c475d47842d67db4f0a7d85d63ae11f9f3c.camel@gmail.com>
2022-08-19 3:33 ` [bug#57280] [PATCH 0/3] Add documentation-files argument to emacs build system Andrew Tropin
2022-08-19 4:19 ` Liliana Marie Prikler
2022-08-19 6:21 ` Andrew Tropin
2022-08-19 15:39 ` Liliana Marie Prikler [this message]
2022-08-26 14:33 ` Andrew Tropin
2022-08-29 16:38 ` Liliana Marie Prikler
2022-08-30 8:15 ` Andrew Tropin
2022-08-30 8:28 ` Liliana Marie Prikler
2022-08-31 9:36 ` Andrew Tropin
2022-08-31 10:07 ` Liliana Marie Prikler
2022-09-02 14:02 ` Andrew Tropin
2022-09-02 14:52 ` Liliana Marie Prikler
2023-04-26 4:40 ` bug#57280: " Andrew Tropin
2022-08-18 18:35 [bug#57280] " Andrew Tropin
2022-08-18 19:31 ` Liliana Marie Prikler
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c76deb583d7ef2d9ecaa173c3c1cdf0a9280aa84.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=57280@debbugs.gnu.org \
--cc=andrew@trop.in \
/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/guix.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).