From: John Darrington <john@darrington.wattle.id.au>
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Should synopsis handle texinfo markup?
Date: Sat, 11 Mar 2017 20:34:07 +0100 [thread overview]
Message-ID: <20170311193407.GA5763@jocasta.intra> (raw)
In-Reply-To: <874lyz396q.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
On Sat, Mar 11, 2017 at 10:27:57PM +0300, Alex Kost wrote:
Hello, I've noticed that several packages contain "@code" structures in
their synopses, but only 'description' field supports texinfo markup.
For example, look at:
guix package -s ruby-minitest-bonus-assertions
So I wonder, should these synopses be adjusted to remove @code things,
or would it be better to make sysnopses support it?
... and, if we decide that synopses may not have Texinfo markup, then we
should have guix lint check for it.
J'
--
Avoid eavesdropping. Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-03-11 19:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-11 19:27 Should synopsis handle texinfo markup? Alex Kost
2017-03-11 19:34 ` John Darrington [this message]
2017-03-15 16:14 ` Ludovic Courtès
2017-03-16 8:53 ` Alex Kost
2017-03-16 22:29 ` Ludovic Courtès
2017-03-20 10:52 ` Alex Kost
2017-03-24 9:38 ` Ludovic Courtès
2017-03-27 7:58 ` Alex Kost
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=20170311193407.GA5763@jocasta.intra \
--to=john@darrington.wattle.id.au \
--cc=alezost@gmail.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).