From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Should synopsis handle texinfo markup?
Date: Thu, 16 Mar 2017 23:29:24 +0100 [thread overview]
Message-ID: <87d1dgua7v.fsf@gnu.org> (raw)
In-Reply-To: <874lyt38nk.fsf@gmail.com> (Alex Kost's message of "Thu, 16 Mar 2017 11:53:03 +0300")
Alex Kost <alezost@gmail.com> skribis:
> Ludovic Courtès (2017-03-15 17:14 +0100) wrote:
>
>> Hi Alex,
>>
>> Alex Kost <alezost@gmail.com> skribis:
>>
>>> 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?
>>
>> Maybe we should support Texinfo in synopses after all. I don’t think
>> there were good reasons not to do it.
>>
>> Thoughts?
>
> I'm not aware of potential problems so I think it would be good to add
> this support to synopses.
Cool. Would you or anyone like to give it a try? Alternatively we can
mail it to bug-guix for later.
Ludo’.
next prev parent reply other threads:[~2017-03-16 22:29 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
2017-03-15 16:14 ` Ludovic Courtès
2017-03-16 8:53 ` Alex Kost
2017-03-16 22:29 ` Ludovic Courtès [this message]
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=87d1dgua7v.fsf@gnu.org \
--to=ludo@gnu.org \
--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).