From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: dana <dana@dana.is>
Cc: Bart Schaefer <schaefer@brasslantern.com>,
Daniel Shahaf <d.s@daniel.shahaf.name>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Official plugin manager?
Date: Fri, 3 Jan 2020 06:13:18 +0100 [thread overview]
Message-ID: <CAKc7PVBnrNnq3J2tZdS9a4SjYXX181Owq1LdL5AS6Vh=zNVLDA@mail.gmail.com> (raw)
In-Reply-To: <12F64C78-BFA2-460C-80D4-921F22C72F78@dana.is>
On Fri, 3 Jan 2020 at 04:24, dana <dana@dana.is> wrote:
>
> On 2 Jan 2020, at 20:43, Sebastian Gniazdowski <sgniazdowski@gmail.com> wrote:
> > Well yes, because I suspect that there will be a rough time on
> > establishing what the defaults are supposed to be.
>
> Right, from what i've heard, that has been an issue in the past. But it needs
> to be done to address this. OMZ did it.
>
> I really do think that novice users don't understand the significance of the
> choices you seem to be proposing (obv), and they don't want to spend 45
> minutes tapping through a wizard to have it explained to them, either. When
> they run zsh for the first time, they just want to see what it can *do* — they
> can change their history-file path later, if they want.
I've now thought that this might be reminiscent of the difference
between package-based Linux distros and Gentoo. When I've switched
recently to the second I've noticed how much freedom there is in how
the programs are installed and I've had some moments of being puzzled
"how do the RPM-based distros actually manage to provide a working
software?" or "how did I live without those options?" The answer is, I
suppose:
- the options (in configure, CMake, etc.) are always aimed at
providing all the available features,
- in case of a conflict situation (like e.g.: libressl vs libopenssl)
a tear-down (of the conflict) decision is being made that e.g.: favors
the more popular library and closes the problem and moves on.
So the history setup that would follow this guidance could be:
HISTFILE=$HOME/.zhistory
HISTSIZE=40000
SAVEHIST=$HISTSIZE
setopt hist_ignore_dups
setopt inc_append_history hist_fcntl_lock
setopt hist_ignore_space
setopt hist_lex_words
That said the param='...' way could be still useful for e.g.:
share_history as it's a different kind of setup, not a feature to
include.
--
Sebastian Gniazdowski
News: https://twitter.com/ZdharmaI
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin
Blog: http://zdharma.org
next prev parent reply other threads:[~2020-01-03 5:14 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
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 [this message]
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='CAKc7PVBnrNnq3J2tZdS9a4SjYXX181Owq1LdL5AS6Vh=zNVLDA@mail.gmail.com' \
--to=sgniazdowski@gmail.com \
--cc=d.s@daniel.shahaf.name \
--cc=dana@dana.is \
--cc=schaefer@brasslantern.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).