public inbox for
 help / color / mirror / Atom feed
From: Gaius Mulley <>
To: "Martin Liška" <>
Subject: Re: [PATCH v2 16/19] modula2 front end: bootstrap and documentation tools
Date: Thu, 24 Nov 2022 14:30:25 +0000	[thread overview]
Message-ID: <875yf4h1by.fsf@debian> (raw)
In-Reply-To: <> ("Martin =?utf-8?Q?Li=C5=A1ka=22's?= message of "Thu, 24 Nov 2022 12:53:02 +0100")

Martin Liška <> writes:

> On 11/8/22 14:22, Gaius Mulley wrote:
>> Martin Liška <> writes:
>> should be good - I'll complete the rst output in the scripts,
> Hi.

Hi Martin,

> As you probably noticed, the Sphinx migration didn't go well.

Yes, sorry to see this didn't happen.  Thank you for your hard work and
I hope it can occur in the future.

> However, it's still up to you if you want to use it or not for Modula
> 2.

Once modula-2 is in master I'd like to revisit rst in devel/modula-2
along with analyzer patches and m2 generics.  If successful then submit
patches in early stage 1.

> We have manuals like libgccjit, or Ada manuals
> that use RST natively and provide exported .texi files.

Ok thanks for the pointers, I will experiment with these build rhunes.

> Cheers and sorry for the troubles I caused.

No problem at all - the modula-2 scripts are now improved and cleaner
due to the port.  Hopefully rst will happen sometime in the future,


  reply	other threads:[~2022-11-24 14:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-10 15:31 [PATCH] 16/19 " Gaius Mulley
2022-10-13  9:12 ` Martin Liška
2022-10-14 12:10   ` Gaius Mulley
2022-11-07 13:09     ` [PATCH v2 16/19] " Gaius Mulley
2022-11-07 13:47       ` Martin Liška
2022-11-08 13:22         ` Gaius Mulley
2022-11-24 11:53           ` Martin Liška
2022-11-24 14:30             ` Gaius Mulley [this message]
2022-11-25 16:25               ` Martin Liška
2022-11-25 17:10               ` David Malcolm
2022-11-27 16:51                 ` Gaius Mulley
2022-10-20 12:42 ` [PATCH] 16/19 " Martin Liška
2022-10-28 13:05   ` Gaius Mulley

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:

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

  git send-email \
    --in-reply-to=875yf4h1by.fsf@debian \ \ \ \

* 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.
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).