From: dana <dana@dana.is>
To: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Cc: Daniel Shahaf <d.s@daniel.shahaf.name>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Official plugin manager?
Date: Thu, 2 Jan 2020 19:36:09 -0600 [thread overview]
Message-ID: <186D63AE-2F2A-41C3-9E09-CEE0714E2B7F@dana.is> (raw)
In-Reply-To: <CAKc7PVAPJQZSsOB8XFrA7PLaP8hyD+TmEQY2qoiA8MkXB6_6JQ@mail.gmail.com>
On 2 Jan 2020, at 18:25, Sebastian Gniazdowski <sgniazdowski@gmail.com> wrote:
> I think that this hits a wall of having a choice. "Hey, I just want a
> *reasonable* p-m to get all the plugins, as that's what actually
> matters, isn't it? Why do I have to decide on the p-m, if I'm going to
> do this properly then I'll at least enter 'best zsh plugin manager' in
> Google, and this means work, work, lost time and large impatience
> intake. And then the slight discomfort of not diving into the topic
> enough deep and deciding on a p-m mostly by its cool name - hey, am I
> really using the p-m that I should?"
Is the problem you're trying to solve 'people don't know which plug-in manager
to use' or 'people don't know how to configure zsh so they just install OMZ'?
The one you're describing here is the former. Once they *have* a plug-in
manager, they can install whatever they want, and they seem to want OMZ. (It's
even the first example in the Antigen documentation...)
On 2 Jan 2020, at 18:25, Sebastian Gniazdowski <sgniazdowski@gmail.com> wrote:
> OK, however, the sourcables-backend to zsh-newuser-install is IMO
> needed first. Then the install function could offer to append:
>
> zsh-pm pick=nodups.zsh param='size -> 10000' @history
>
> to the zshrc.
You've responded to me saying 'instead of providing fine control over the
profile set-up it could simply give them some good defaults' with 'OK, but
first we need to add more complexity in order to provide finer control over
the profile set-up'
Also, your example command is about 20 characters longer, and significantly
harder to read or to transfer into a broader understanding of how the shell
configuration works, than just setting it the normal way. How would this
address the difficulty me and Roman described re: not understanding the
implications of the wizard?
dana
next prev parent reply other threads:[~2020-01-03 1:34 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 3:17 Sebastian Gniazdowski
2020-01-02 4:28 ` Eric Cook
2020-01-02 11:03 ` Daniel Shahaf
2020-01-02 11:37 ` Sebastian Gniazdowski
2020-01-02 11:55 ` Sebastian Gniazdowski
2020-01-02 21:30 ` dana
2020-01-03 0:25 ` Sebastian Gniazdowski
2020-01-03 1:36 ` dana [this message]
2020-01-03 2:43 ` Sebastian Gniazdowski
2020-01-03 2:45 ` Bart Schaefer
2020-01-03 3:26 ` dana
2020-01-03 5:13 ` Sebastian Gniazdowski
2020-01-03 15:00 ` Peter Stephenson
2020-01-03 20:48 ` Daniel Shahaf
2020-01-03 21:51 ` Roman Perepelitsa
2020-01-03 22:06 ` Daniel Shahaf
2020-01-03 22:26 ` Bart Schaefer
2020-01-03 22:37 ` Roman Perepelitsa
2020-01-04 0:42 ` dana
2020-01-04 1:06 ` Daniel Shahaf
2020-01-04 15:46 ` Roman Perepelitsa
2020-01-04 16:27 ` Daniel Shahaf
2020-01-04 16:41 ` Roman Perepelitsa
2020-01-04 17:35 ` Daniel Shahaf
2020-01-04 17:42 ` Roman Perepelitsa
2020-01-04 17:11 ` Bart Schaefer
2020-01-05 10:40 ` Oliver Kiddle
2020-01-06 17:47 ` Leah Neukirchen
2020-01-03 11:15 ` Oliver Kiddle
2020-01-04 5:16 ` Sebastian Gniazdowski
2020-01-04 6:00 ` Sebastian Gniazdowski
2020-01-02 12:00 ` Roman Perepelitsa
2020-01-02 12:21 ` Sebastian Gniazdowski
2020-01-02 12:27 ` Roman Perepelitsa
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=186D63AE-2F2A-41C3-9E09-CEE0714E2B7F@dana.is \
--to=dana@dana.is \
--cc=d.s@daniel.shahaf.name \
--cc=sgniazdowski@gmail.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).