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 06036ad7 for ; Thu, 2 Jan 2020 03:18:30 +0000 (UTC) Received: (qmail 7194 invoked by alias); 2 Jan 2020 03:18:25 -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: 45185 Received: (qmail 21799 invoked by uid 1010); 2 Jan 2020 03:18:25 -0000 X-Qmail-Scanner-Diagnostics: from mail-vs1-f45.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.217.45):SA:0(-2.0/5.0):. Processed in 1.289958 secs); 02 Jan 2020 03:18:25 -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.217.45 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:from:date:message-id:subject:to :content-transfer-encoding; bh=7i0KsFgUQDbVSmUMs4U+/X3dDpD16gXXjKrGj41Wz/A=; b=kftS1r0KbrqMzM0bka83nJFT4fB8WvTNUk/t7m16IUtaNKdyqQBXQxV7XIojCl7r6F ibgMgKvMnwEVUNk/T+qIUPRyPqj3UqKwHfD2M/FZPiGrcoBYlA98tnq2il5fQNzLgCEf bhkTHjYGBP1rMrU3u08HvWDe9WYmggCTTaTp6jhN+PbXTOBxYazdLY8cGdrnMOFuKBbP /w8I7whA8m8cLRaiq5v1/QdX9qC8fNkTQwLUPa6w2FnvM4VIzKOzg/I5q3X4Ew06W/Uf Nt0BCzTZrWUx0Jz8A0g3IL8Ge7w9vT8WMHSQxv1EeosJqa9Ky9syQzhzN+/T8Kw1caS8 ty+A== X-Gm-Message-State: APjAAAUmG6NrwVWvCjTHF9MZDZ886f0SZeAHlgYWlkV7rgnrOomfrnyd MMFxDuLGFAXJiT1Yc7n+/D37R2AQq2BDszYmPdTL2po9 X-Google-Smtp-Source: APXvYqzZewJOga9Ni/fenF0Fpboc3N4vBPCLx2jAe3CszQLVvtn2Y/zQj7Hec+jH247GVzgDRR4fi3Xbj+4tnyoWUw0= X-Received: by 2002:a67:c582:: with SMTP id h2mr40742975vsk.77.1577935070074; Wed, 01 Jan 2020 19:17:50 -0800 (PST) MIME-Version: 1.0 From: Sebastian Gniazdowski Date: Thu, 2 Jan 2020 04:17:41 +0100 Message-ID: Subject: Official plugin manager? To: Zsh hackers list Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi After a brief discussion on IRC, I thought about advantages of an official p-m being available. Maybe it's the right time to glance over them? 1. The example, bootstrapping zshrcs shared on the net would be resulting in feature-complete setups, with e.g.: a feature-rich nice prompt, syntax-highlighting of the command line and e.g.: of the history, etc. 2. This could be actually addressing the issue that zsh-newuser-install aims at solving: to easily bootstrap a new zsh user's setup. 3. It would offload the situation that "you cannot use Zsh without Oh My Zsh" or "... without a plugin manager". Today many Zsh users feel that they "couldn't make it" without Oh My Zsh because Zsh is a complex system that needs a ground of sane settings. With the official p-m, the situation would not have been of "laying a ground of sane settings", but of "loading a well-written prompt", for example, and it's a different-quality situation. 4. The new users wouldn't have to go through the somewhat stressful stage of selecting a framework. The stress comes from having a choice, as there are many p-ms available (antibody, antigen, zgen, zplug, zplugin to name a few). The users could wait with the need of switching to a custom p-m for the moment when they will feel that they're ready to (if they do). 5. Coding such p-m will be a very good time for the people involved (which I hope would involve Peter, Bart, Oliver, Daniel, Mikael, Roman and others). 6. It would allow establishing a way of distributing Zsh scripts in a different way than the autoload functions =E2=80=93 by a kind of a package = of files in a subdirectory, The method would have been a step forward and it would allow contributing such objects to Zsh as currently, it requires tricks like in the prompt function, which rather closes the way for such new contributions, as they are not fully nice (the prompt function is, however, a nice engineering, but that's a special case). What do you think? Could the official plugin manager project be starting for 5.9? To then gain a full feature set before 6.0? (I'm making a slight point here that the p-m would be a good front-end reason for releasing the next major version). --=20 Sebastian Gniazdowski News: https://twitter.com/ZdharmaI IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin Blog: http://zdharma.org