zsh-workers
 help / color / mirror / code / Atom feed
From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Official plugin manager?
Date: Fri, 3 Jan 2020 22:51:13 +0100	[thread overview]
Message-ID: <CAN=4vMrce+DE9s1gKwXmyYkwW_de=7SwffumaNnDmpG3+uj1Mg@mail.gmail.com> (raw)
In-Reply-To: <20200103204856.bv6f3dkqhtrjm6vm@tarpaulin.shahaf.local2>

On Fri, Jan 3, 2020 at 10:06 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> P.S. Some ideas for what to have there:
>
> - PS1

This is just my personal opinion that I don't hold very strongly and
my voice obviously carries little weight here. I think zshrc
recommended by zsh should be very conservative. It should enable users
to get started (basic keys must work, prompt must show current
directory, completions must work -- this sort of stuff) *and* it must
enable average users to take control over their configuration. The
danger of too complex starter zshrc is that users won't be able to
understand it, and will have worse setup long term because of this.

To be more specific:

- no vcs_info. in some environments it makes prompt noticeably slow;
it also adds a lot of complexity
- the config itself must not have any configuration options of its
own, be it zstyle or parameters; it's a config, not a meta config;
users should be encouraged to edit it rather than create another
config with parameters for this config and source one from another
- no prompt_subst or precmd hooks
- no prompt shortening; display directory as %~
- no syntax highlighting, autosuggestions or any other external
plugins; autoloading functions bundled with zsh is OK
- single file (zshrc)

The file should explain through comments what things mean ("%~ is
current directory", etc) and should suggest where users should add
their aliases and exported variables. Comments should also suggest
where more information can be found ("for more information about
prompting, see xxx"). Links to web pages here work better than `man`
commands, although putting both of them will also work.

What about the goodies though? Leave that to the market. Anyone can
come up with a config template, or even an interactive dialog that
creates a config based on your preferences. Let them compete. zsh
should be *usable* upon installation but not bloated or opinionated.

Just my 2 cents. You may notice that my opinions here can be summed up
as "do what Bash does" without much loss of fidelity.

Roman.

  reply	other threads:[~2020-01-03 21:52 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
2020-01-03 15:00               ` Peter Stephenson
2020-01-03 20:48                 ` Daniel Shahaf
2020-01-03 21:51                   ` Roman Perepelitsa [this message]
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='CAN=4vMrce+DE9s1gKwXmyYkwW_de=7SwffumaNnDmpG3+uj1Mg@mail.gmail.com' \
    --to=roman.perepelitsa@gmail.com \
    --cc=d.s@daniel.shahaf.name \
    --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).