From: Gaius Mulley <gaiusmod2@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Modula-2: merge followup (brief update on the progress of the new linking implementation)
Date: Thu, 08 Sep 2022 16:52:20 +0100 [thread overview]
Message-ID: <87mtb9dft7.fsf@debian> (raw)
In-Reply-To: <ab56933d-61b1-d351-a5e1-c8aae83052e8@suse.cz> ("Martin =?utf-8?Q?Li=C5=A1ka=22's?= message of "Wed, 7 Sep 2022 14:29:06 +0200")
Martin Liška <mliska@suse.cz> writes:
> Note I've just converted the current Modula-2 manual to RST (Sphinx):
> https://splichal.eu/scripts/sphinx/
>
> It contains some minor issues, but in general it should be pretty fine. Note pygments
> contains a corresponding lexer:
> https://pygments.org/docs/lexers/#multi-dialect-lexer-for-modula-2
very nice - well done! All very useful - and much easier to see bugs in
gm2.texi. I see a few missing options (missing from gm2.texi) and also
I see problems with the libraries - meta data (const/type/var) is
rendered (@findex perhaps should be ignored or processed). Or I could
disable it from gcc/m2/tools-src/def2texi.py)?
It is starting to look very nice indeed
regards,
Gaius
next prev parent reply other threads:[~2022-09-08 15:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 10:31 Gaius Mulley
2022-07-11 8:21 ` Rainer Orth
2022-07-11 11:14 ` Rainer Orth
2022-07-11 15:06 ` Gaius Mulley
2022-07-11 20:36 ` Rainer Orth
2022-07-12 12:32 ` Gaius Mulley
2022-07-12 14:16 ` Rainer Orth
2022-07-25 9:42 ` Gaius Mulley
2022-07-26 7:45 ` Rainer Orth
2022-08-30 11:03 ` Gaius Mulley
2022-08-30 12:44 ` Martin Liška
2022-08-30 15:36 ` Gaius Mulley
2022-08-31 9:54 ` Martin Liška
2022-08-31 13:19 ` Gaius Mulley
2022-08-31 13:25 ` Martin Liška
2022-09-01 12:22 ` Gaius Mulley
2022-09-07 12:29 ` Martin Liška
2022-09-08 15:52 ` Gaius Mulley [this message]
2022-09-09 12:16 ` Martin Liška
2022-09-09 15:40 ` Gaius Mulley
-- strict thread matches above, loose matches on Subject: below --
2022-06-11 19:15 Gaius Mulley
2022-06-17 17:08 ` Gaius Mulley
2022-06-17 19:02 ` Richard Biener
2022-06-27 7:24 ` 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:
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=87mtb9dft7.fsf@debian \
--to=gaiusmod2@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
/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.
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).