From: RunningDroid <RunningDroid@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: runit: Remove zsh completions
Date: Thu, 27 Oct 2022 23:29:05 +0200 [thread overview]
Message-ID: <20221027212905.AsdakWS13F1bF1ndN6K_aVUMslpRzhSGWafRu_y2m5g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36593@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
New comment by RunningDroid on void-packages repository
https://github.com/void-linux/void-packages/issues/36593#issuecomment-1294083479
Comment:
Sorry for bumping a stale issue, but I wanted to point out that (after https://github.com/void-linux/runit/pull/15 is merged) neither completion is better than the other (IMO.)
The completion from zsh-users has prettier prompts, but it doesn't ignore `$SVDIR` when using `sudo`\*.
The completion that we (will) ship with runit (that we apparently have 2 copies of) ignores `$SVDIR` when using `sudo`\*, but it has relatively minimalist prompts.
The good news is that the licenses between the two completions [appears to be](https://en.wikipedia.org/wiki/License_compatibility#/media/File:Floss-license-slide-image.svg) compatible, runit is licensed BSD-3-CLAUSE & the zsh-users completion appears to be licensed MIT, so we (aka void-linux/runit) can copy the fancy prompts but I don't think they can copy the `sudo`\* detection without re-licensing their completions.
\*:and `su -c`, and `doas`
next prev parent reply other threads:[~2022-10-27 21:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 2:18 [ISSUE] " foopub
2022-04-09 2:25 ` foopub
2022-07-09 2:14 ` github-actions
2022-07-23 2:14 ` [ISSUE] [CLOSED] " github-actions
2022-10-27 21:29 ` RunningDroid [this message]
2023-01-18 19:45 ` leahneukirchen
2023-04-19 1:54 ` github-actions
2023-05-04 1:51 ` [ISSUE] [CLOSED] " github-actions
2023-06-16 12:26 ` leahneukirchen
2023-04-01 13:40 [PR PATCH] runit: remove " mhmdanas
2023-04-02 12:04 ` leahneukirchen
2023-04-13 0:30 ` classabbyamp
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=20221027212905.AsdakWS13F1bF1ndN6K_aVUMslpRzhSGWafRu_y2m5g@z \
--to=runningdroid@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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).