From: Guillaume Le Vaillant <glv@posteo.net>
To: Jack Hill <jackhill@jackhill.us>
Cc: 48485@debbugs.gnu.org, Sharlatan Hellseher <sharlatanus@gmail.com>
Subject: [bug#48485] [PATCH 1/2]: gnu: Add shasht
Date: Tue, 18 May 2021 16:40:54 +0000 [thread overview]
Message-ID: <87o8d8uh9l.fsf@kitej> (raw)
In-Reply-To: <alpine.DEB.2.21.2105181145560.2109@marsh.hcoop.net>
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
Jack Hill <jackhill@jackhill.us> skribis:
> Thanks for working on this. However, I have a question about the synopsis:
>
>> + (synopsis "Common Lisp JSON reading and writing for the Kzinti")
>
> As a native American English speaker, I find Kzinti to be an obscure word.
> I didn't know what it meant when I first read it. Doing a search online
> wasn't that enlightening. The best thing I could fine talked about alien cats
> [0]. Do you think the synopsis could be improved in the future to more clearly
> say what the software is for and improve search results? Perhaps shortening it
> to "Common Lisp JSON reading and writing" would be sufficient?
>
> [0] https://en.wikipedia.org/wiki/Kzin
>
> Best,
> Jack
Before pushing Sharlatan's patch, I changed the synopsis to "Common Lisp
JSON reading and writing library". I also didn't know that word, found
that it was probably a reference to a cat-looking warrior from space in
a series of science fiction novels, and concluded that it was not
really related to JSON processing.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-05-18 16:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 19:48 [bug#48485] [PATCH 2/2]: gnu: common-lisp-jupyter: Update to 0.1.0-3.ba9f0e7 Sharlatan Hellseher
2021-05-17 19:54 ` [bug#48485] [PATCH 1/2]: gnu: Add shasht Sharlatan Hellseher
2021-05-18 7:52 ` bug#48485: " Guillaume Le Vaillant
2021-05-18 15:58 ` [bug#48485] " Jack Hill
2021-05-18 16:40 ` Guillaume Le Vaillant [this message]
2021-05-18 16:50 ` Jack Hill
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=87o8d8uh9l.fsf@kitej \
--to=glv@posteo.net \
--cc=48485@debbugs.gnu.org \
--cc=jackhill@jackhill.us \
--cc=sharlatanus@gmail.com \
/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.