From: Mathieu Lirzin <mthl@gnu.org>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/2] gnu: atlas: Use cpupower in description.
Date: Fri, 29 Jul 2016 10:22:58 +0200 [thread overview]
Message-ID: <87twf87t0d.fsf@gnu.org> (raw)
In-Reply-To: <87bn1h4bel.fsf@we.make.ritual.n0.is> (ng0@we.make.ritual.n0.is's message of "Thu, 28 Jul 2016 22:59:14 +0000")
Hello,
ng0 <ng0@we.make.ritual.n0.is> writes:
> Mathieu Lirzin <mthl@gnu.org> writes:
>
>> Tobias Geerinckx-Rice <me@tobias.gr> writes:
>>
>>> Ludo',
>>>
>>> On 2016-07-19 23:00, ludo@gnu.org wrote:
>>>> Applied, thanks!
>>>
>>> Thanks! I didn't know about @example.
>>>
>>> It seems like some Texinfo syntax is encouraged (like @command), but
>>> not the full set (package descriptions are full of abbreviations,
>>> but no @abbr or @acronym anywhere). Is this by design?
>>
>> Nope it is not by design, the Guile (texinfo ...) modules just don't
>> implement these commands from GNU Texinfo, but should indeed.
>>
>> --
>> Mathieu Lirzin
>>
>
> Is there a feature request / bug we could file somewhere on this? I
> don't know what the upstream of Guile texinfo is, but it reads like it
> should be extended.
Guile texinfo is maintained in Guile itself. You can send a bug report
to <bug-guile@gnu.org>.
Thanks!
--
Mathieu Lirzin
next prev parent reply other threads:[~2016-07-29 8:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 2:45 [PATCH 0/2] Add cpupower Tobias Geerinckx-Rice
2016-07-19 2:45 ` [PATCH 1/2] gnu: " Tobias Geerinckx-Rice
2016-07-19 20:59 ` Ludovic Courtès
2016-07-19 21:13 ` Tobias Geerinckx-Rice
2016-07-19 22:01 ` Eric Bavier
2016-07-19 2:45 ` [PATCH 2/2] gnu: atlas: Use cpupower in description Tobias Geerinckx-Rice
2016-07-19 21:00 ` Ludovic Courtès
2016-07-19 21:33 ` Tobias Geerinckx-Rice
2016-07-19 21:47 ` Mathieu Lirzin
2016-07-28 22:59 ` ng0
2016-07-29 8:22 ` Mathieu Lirzin [this message]
2016-07-29 8:35 ` ng0
2016-08-14 6:24 ` Pjotr Prins
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=87twf87t0d.fsf@gnu.org \
--to=mthl@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ng0@we.make.ritual.n0.is \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.