From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id c15cb567 for ; Fri, 3 Jan 2020 05:14:08 +0000 (UTC) Received: (qmail 10308 invoked by alias); 3 Jan 2020 05:14:01 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 45207 Received: (qmail 27911 invoked by uid 1010); 3 Jan 2020 05:14:01 -0000 X-Qmail-Scanner-Diagnostics: from mail-ua1-f65.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.1/25677. spamassassin: 3.4.2. Clear:RC:0(209.85.222.65):SA:0(-2.0/5.0):. Processed in 1.107999 secs); 03 Jan 2020 05:14:01 -0000 X-Envelope-From: sgniazdowski@gmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.222.65 as permitted sender) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=6ys99hdYTwywk29JZucjcGAdFocWpmsMbPqCe98QkbE=; b=JUz5dTZ2FvoVLGuWQLScxvUg1YBFJfXPuEyeUXbHIeKNOKYv++UWgND6oClbcjro0p w5FZEjv4mRyfmysXKJgT2IGShGjPUahKu69316wH0Y4Kqv1NI7xSoQmioYiOU6xh4QT4 RxecoRtEtaQoYQen8UYZxfoNdYqAf41btbusBuduSretXq1Gtm+uIG8BIjE+YnrlS9WP Ri1HwoszrftYUBd8115Hgvki6GucuJcT+A3KR+4nmG1M4tLKwmeY84A1sumTOSHJg16m jSWcpHuDwDDYcssPuzxY/oAfJ50ozh823L05AZjTzTokdi+M5t+pbv/4Z0yILdXWE7Uy 2Eog== X-Gm-Message-State: APjAAAWAymVyLAL7vOH+mf4KzCU6vb7Dh2VLwmbVWCYgN2Qt5SFjncxo WDWHkQl9Rt2+nwprYk+5HiwJqCMzekWnnhC7T1o= X-Google-Smtp-Source: APXvYqzkoFyIx3Uhgm6MSnE/550S3JIpp9zgAnwgTGtnAEozMg3Gx7RNF5gkbzFNrY1Lq3SW2mPoQ7l68TtwItKqKFw= X-Received: by 2002:ab0:6954:: with SMTP id c20mr47051353uas.82.1578028406310; Thu, 02 Jan 2020 21:13:26 -0800 (PST) MIME-Version: 1.0 References: <63663202-4b1d-428a-b16b-5be1425e84ef@www.fastmail.com> <0C0C9775-59EE-4FBB-AB84-3E7FEF6E5024@dana.is> <186D63AE-2F2A-41C3-9E09-CEE0714E2B7F@dana.is> <12F64C78-BFA2-460C-80D4-921F22C72F78@dana.is> In-Reply-To: <12F64C78-BFA2-460C-80D4-921F22C72F78@dana.is> From: Sebastian Gniazdowski Date: Fri, 3 Jan 2020 06:13:18 +0100 Message-ID: Subject: Re: Official plugin manager? To: dana Cc: Bart Schaefer , Daniel Shahaf , Zsh hackers list Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 3 Jan 2020 at 04:24, dana wrote: > > On 2 Jan 2020, at 20:43, Sebastian Gniazdowski w= rote: > > 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 n= eeds > 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. Wh= en > they run zsh for the first time, they just want to see what it can *do* = =E2=80=94 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=3D$HOME/.zhistory HISTSIZE=3D40000 SAVEHIST=3D$HISTSIZE setopt hist_ignore_dups setopt inc_append_history hist_fcntl_lock setopt hist_ignore_space setopt hist_lex_words That said the param=3D'...' way could be still useful for e.g.: share_history as it's a different kind of setup, not a feature to include. --=20 Sebastian Gniazdowski News: https://twitter.com/ZdharmaI IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin Blog: http://zdharma.org