From: Luis Felipe <sirgazil@zoho.com>
To: guix-devel@gnu.org
Subject: Re: IDEA: missing-tests-pypi-error? condition
Date: Sun, 8 Oct 2023 16:17:44 +0000 [thread overview]
Message-ID: <1ba1325b-9218-2bf3-6a6f-e9dc2db3e446@zoho.com> (raw)
In-Reply-To: <bc6a8640089148e3c369e4d97b32fb63@dismail.de>
[-- Attachment #1.1.1: Type: text/plain, Size: 811 bytes --]
Hi,
El 8/10/23 a las 13:11, jgart escribió:
> Doing info texinfo is TMI:
>
> https://up.nixnet.services/7tzldvyw.png
According to the Guix manual
(https://guix.gnu.org/es/manual/devel/en/html_node/Writing-Documentation.html),
people is encouraged to contribute documentation in any format.
So how about filing an issue (with CC to guix-devel) for this particular
case and propose changes or additions in plain prose? Maybe someone else
can help format the result and provide a patch.
Also, for what it's worth, I have a project whose documentation is kinda
like a summary of Texinfo elements (commands). Maybe it is between TMI
and TLI?
Source: https://codeberg.org/luis-felipe/texinfo-css
HTML: https://luis-felipe.gitlab.io/texinfo-css/
See the Elements section.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2881 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2023-10-08 16:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 13:08 IDEA: missing-tests-pypi-error? condition jgart
2023-10-06 9:09 ` Munyoki Kilyungi
2023-10-06 13:03 ` Maxim Cournoyer
2023-10-06 15:00 ` Munyoki Kilyungi
2023-10-07 16:07 ` Maxim Cournoyer
2023-10-08 13:11 ` jgart
2023-10-08 16:17 ` Luis Felipe [this message]
2023-10-09 0:52 ` Maxim Cournoyer
2023-10-09 13:36 ` Josselin Poiret
2023-10-09 13:57 ` jgart
2023-10-09 17:17 ` Maxim Cournoyer
2023-10-12 5:49 ` Efraim Flashner
2023-10-06 11:10 ` jgart
2023-10-06 12:50 ` Munyoki Kilyungi
2023-10-07 16:05 ` Maxim Cournoyer
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=1ba1325b-9218-2bf3-6a6f-e9dc2db3e446@zoho.com \
--to=sirgazil@zoho.com \
--cc=guix-devel@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/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).