From: Kei Kebreau <kkebreau@posteo.net>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 32256@debbugs.gnu.org
Subject: [bug#32256] [PATCH] gnu: Add nudoku.
Date: Fri, 17 Aug 2018 03:44:13 -0400 [thread overview]
Message-ID: <87o9e130aa.fsf@posteo.net> (raw)
In-Reply-To: <87sh3eclbc.fsf@tobias.gr> (Tobias Geerinckx-Rice's message of "Thu, 16 Aug 2018 18:45:11 +0200")
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
Tobias Geerinckx-Rice <me@tobias.gr> writes:
> Kei,
>
> Just an aside on this important matter.
>
> Kei Kebreau wrote:
>>> + (description "nudoku is a ncurses based sudoku game.")
>>
>> I'd use "@code{nudoku}" here because it's the name of a program.
>
> While there's some precedent in Guix for using @code{} for marking up
> package names when they'll be used mainly in actual source code
> (e.g. @code{My::Perl::Module}), that's a specific case with a specific
> rationale.
>
> A more suitable tag here would be @command{}. However, there seems to
> be an informal(?) consensus not to use it when talking about the
> package as a whole/project, but only when referring to the actual
> command (binary) itself. Some descriptions don't follow that
> convention, though, so it's at best a grey area.
>
> I don't think programme names should be marked up all purdy just for
> being programmes.
>
> Kind regards,
>
> T G-R
Alright. Hopefully I'll pick up more on these hints as I read more
documentation source code.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2018-08-17 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 12:04 [bug#32256] [PATCH] gnu: Add nudoku Ricardo Wurmus
2018-07-26 20:15 ` Kei Kebreau
2018-08-16 15:07 ` bug#32256: " Ricardo Wurmus
2018-08-16 16:45 ` [bug#32256] " Tobias Geerinckx-Rice
2018-08-17 7:44 ` Kei Kebreau [this message]
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=87o9e130aa.fsf@posteo.net \
--to=kkebreau@posteo.net \
--cc=32256@debbugs.gnu.org \
--cc=me@tobias.gr \
/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.