From: Yuri D'Elia <wavexx@thregr.org>
To: zsh-users@zsh.org
Subject: Re: zsh-newuser-install
Date: Wed, 23 Apr 2014 22:31:46 +0200 [thread overview]
Message-ID: <lj984r$6uo$1@ger.gmane.org> (raw)
In-Reply-To: <20140423165024.1480528a@pws-pc.ntlworld.com>
On 04/23/2014 05:50 PM, Peter Stephenson wrote:
> There's certainly plenty that could be added here --- enough that
> nothing's likely to happen unless we get some solid feedback...
>
> - Make it more modular so stuff can be plugged into it and more of the
> low-level framework is available as separate functions.
>
> - Make it interact better with scripts installed by distributions? I'm
> not sure how useful this actually is, given distributions tend to hook
> into to global /etc files, but then that doesn't give the user much
> control, which is the point of newuser. Maybe the previous point already
> covers this well enough.
I'd like to plug myself right in here, to mention that I find the
newuser module to be frustrating once you _already_ know zsh.
It'd like it to be just a function being called in /etc/zsh/zshrc with a
simple test:
[ ! -f "~/.zshrc" ] && zmodload ... && zsh-newuser-install
So that:
- you can re-run it manually whenever you want (just zmodload&call)
- you can disable the check by editing the systemwide zshrc
... and since configuration files in /etc/ are preserved, the change
would _persist_ when zsh is updated.
Right now I'm using a post-install hook to remove the newuser module
after zsh is updated, because there are a few cases when I don't want a
zshrc around, and I really (really) know what I'm doing.
> These are all merely ideas, they are not things I would intend to do
> just because I felt like it.
I think many people nowdays wouldn't need the newuser mechanism, to be
honest. With oh-my-zsh (and friends), people just look for a
pre-configured solution which has a gazillion of options turned on.
I personally always did the opposite, by starting reading the manual
from an empty rc.
Either way, I think that the newuser mechanism is not actually "selling"
zsh to both experienced or novel users. The only thing that I see, is
that it signals to the user that "look! this is *NOT* bash", and I think
it's actually good to have for places where zsh is unexpected (note: I
*never* saw zsh being the default shell anywhere).
But that's just my 2c.
next prev parent reply other threads:[~2014-04-23 20:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 14:35 setopt interactivecomments shawn wilson
2014-04-16 17:27 ` Bart Schaefer
2014-04-16 17:37 ` shawn wilson
2014-04-17 14:37 ` Ray Andrews
2014-04-17 19:37 ` Bart Schaefer
2014-04-17 21:36 ` Ray Andrews
2014-04-17 22:07 ` shawn wilson
2014-04-17 22:48 ` Bart Schaefer
2014-04-17 23:51 ` shawn wilson
2014-04-17 22:41 ` Bart Schaefer
2014-04-18 3:10 ` Ray Andrews
2014-04-18 11:59 ` Roman Neuhauser
2014-04-23 15:50 ` zsh-newuser-install Peter Stephenson
2014-04-23 20:31 ` Yuri D'Elia [this message]
2014-04-23 23:53 ` zsh-newuser-install Mikael Magnusson
2014-04-24 6:23 ` zsh-newuser-install Yuri D'Elia
2014-04-24 14:34 ` zsh-newuser-install Ray Andrews
2014-04-24 16:02 ` zsh-newuser-install Yuri D'Elia
2014-04-25 1:38 ` zsh-newuser-install Ray Andrews
2014-04-24 16:04 ` zsh-newuser-install Axel Beckert
2014-04-25 15:43 ` zsh-newuser-install Martin Vaeth
2014-04-25 16:21 ` zsh-newuser-install Peter Stephenson
2014-04-26 10:07 ` zsh-newuser-install Martin Vaeth
2014-04-26 20:21 ` zsh-newuser-install Peter Stephenson
2014-04-26 20:38 ` zsh-newuser-install Bart Schaefer
2014-04-25 17:03 ` zsh-newuser-install Bart Schaefer
2014-04-26 13:49 ` zsh-newuser-install Yuri D'Elia
2014-04-26 21:10 ` zsh-newuser-install Bart Schaefer
2014-04-28 17:35 ` zsh-newuser-install Bart Schaefer
2014-04-24 1:05 ` zsh-newuser-install Ray Andrews
2014-04-17 19:04 ` setopt interactivecomments Bart Schaefer
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='lj984r$6uo$1@ger.gmane.org' \
--to=wavexx@thregr.org \
--cc=zsh-users@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).