From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Eric Cook <llua@gmx.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Completion for aplay from alsa-utils
Date: Mon, 25 Nov 2019 10:27:48 +0100 [thread overview]
Message-ID: <CAKc7PVAQo9Qg2uUt5QpBgNMdTEhcm69RznnvV_GqmTB1Rm8_DA@mail.gmail.com> (raw)
In-Reply-To: <db1c1189-8d2a-da85-5fee-f489227ca64b@gmx.com>
[-- Attachment #1: Type: text/plain, Size: 753 bytes --]
Sun., 24 Nov 2019, 23:51 user Eric Cook <llua@gmx.com> wrote:
> You have created:
> - a plugin manager
> - a backdoor for executing commands across separately running zsh processes
> - a json parser
> - a ncurses interface
> - a documentation format
>
> And adding descriptions to a completer is the overwhelming task?
>
I think that yes, it would be. Think rephrasing one sentence in the name of
"not making the work look like if I've just copy-pasted someone's else
text" (as this is what's the topic is about, I suspect). It's fine to do
so. However, after a few next sentences what's this starts to be is "why I
am doing this? isn't it that the authors of the package knew best what the
options are for?" and this IMO quickly starts to overwhelm.
prev parent reply other threads:[~2019-11-25 9:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-02 21:13 Sebastian Gniazdowski
2019-11-03 23:17 ` dana
2019-11-04 10:38 ` Oliver Kiddle
2019-11-21 23:10 ` Sebastian Gniazdowski
2019-11-22 3:05 ` dana
2019-11-25 10:16 ` Sebastian Gniazdowski
2019-11-25 12:10 ` Sebastian Gniazdowski
2019-11-26 2:16 ` dana
2019-12-01 21:11 ` Sebastian Gniazdowski
2019-11-22 15:17 ` Eric Cook
2019-11-25 9:27 ` Sebastian Gniazdowski [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=CAKc7PVAQo9Qg2uUt5QpBgNMdTEhcm69RznnvV_GqmTB1Rm8_DA@mail.gmail.com \
--to=sgniazdowski@gmail.com \
--cc=llua@gmx.com \
--cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).