From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: Official plugin manager?
Date: Fri, 3 Jan 2020 20:48:56 +0000 [thread overview]
Message-ID: <20200103204856.bv6f3dkqhtrjm6vm@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <1578063609.4581.6.camel@samsung.com>
Peter Stephenson wrote on Fri, Jan 03, 2020 at 15:00:09 +0000:
> On Thu, 2020-01-02 at 21:26 -0600, dana wrote:
> > On 2 Jan 2020, at 20:45, Bart Schaefer <schaefer@brasslantern.com> wrote:
> > >
> > > It has been our long-standing practice to recommend that package
> > > builders/installers do NOT create /etc/z* files, or make them minimal,
> > > so as not to interfere with users own initialization files. Maybe
> > > it's time to relax that, or at least to provide a suggested skeleton
> > > .zshrc -- which we could connect to zsh-newuser-install to be slurped
> > > in without having to go through all the questions if you just want to
> > > "feel lucky".
> > The latter is what i'm suggesting, yeah. Dumb down the wizard a bit, add a
> > flashy option to the first screen that says 'do the cool things (recommended)'
> > or whatever, and have it install a well-commented .zshrc with the settings
> > that that a novice/casual user would look for.
>
> I tend to agree with the thrust of this --- feedback over the years has
> been quite strongly people don't want to do anything clever; the difficulty
> remaining is what sort of basic set up to copy in instead. But yes,
> whatever that is it should probably be something prepared elsewhere and
> copying in that should probably be the highlighted / default option.
I agree: my take-away from the discussion is that there's room for a "sensible
defaults" thingy (be it a zshrc template or a plugin). Shall we create
a github/gitlab repo to work on that in?
Cheers,
Daniel
P.S. Some ideas for what to have there:
- compinit
- PS1
(what to include? %m, %~, $SHLVL, %?, $(tty)? Probably have zstyle's or something to enable/disable parts of that.)
- vcs_info
[Some additional vcs_info settings? E.g., during rebases I show the topmost
applied-patch (= the one that conflicted); I think that's not the default…]
- a certain syntax highlighting plugin :P
next prev parent reply other threads:[~2020-01-03 21:06 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 [this message]
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=20200103204856.bv6f3dkqhtrjm6vm@tarpaulin.shahaf.local2 \
--to=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).