zsh-workers
 help / color / mirror / code / Atom feed
From: Marlon <marlon.richert@gmail.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: "İsmail Dönmez" <idoenmez@suse.de>,
	"Arseny Maslennikov" <arseny@altlinux.org>,
	"Kamil Dudka" <kdudka@redhat.com>,
	"Zsh hackers list" <zsh-workers@zsh.org>
Subject: Re: Rewrite of zsh-newuser-install (Mikael's subthread)
Date: Sat, 10 Apr 2021 14:23:32 +0300	[thread overview]
Message-ID: <15283D59-F7B5-4A4C-AFFA-B9D3BB46963F@gmail.com> (raw)
In-Reply-To: <20210407162447.GB6316@tarpaulin.shahaf.local2>


> On 7 Apr 2021, at 19:24, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> 
> I think there's a distinction to be drawn between "stuff we should
> enable in the default zshrc" and "cool stuff that people might want to
> use, or read to learn about useful tricks/features".
> 
> I agree with Mikael and Bart that most of your zshrc falls under the
> latter category.  That has its place (cf. Misc/vcs_info-examples), but
> it's too magical for the default.
> 
> That's also one of the standard criticisms against oh-my-zsh, by the way.

I have heard many criticism against OMZ, but it being “too magical” is new to me. What exactly do you mean with that?


>> Some quotes:
>> 
>> "this zshrc offers a lot of tricks I personally wanted to use but didn't know they were already implemented; thanks a lot for shining a light on them!”
>> 
>> "I gave it a spin and it looks very nice, much less scary than the default one. I've checked the default .zshrc and it looks fine to me."
> 
> If the author of the second quote wishes to join this thread, they're of
> course welcome to do so.  They might change their opinion, or change
> ours.

I’ve now CC’d them, plus the others from which I’ve gotten feedback, on this email.



  reply	other threads:[~2021-04-10 11:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-05 19:44 Mikael Magnusson
2021-04-05 21:01 ` Mikael Magnusson
2021-04-05 21:44 ` Bart Schaefer
2021-04-07 13:44   ` Marlon
2021-04-07 16:24     ` Daniel Shahaf
2021-04-10 11:23       ` Marlon [this message]
2021-04-10 20:46         ` dana
2021-04-10 21:41           ` Bart Schaefer
2021-04-10 22:03             ` Roman Perepelitsa
2021-04-11 11:38               ` Marlon Richert
2021-04-13 14:49               ` Daniel Shahaf
2021-04-13 14:55           ` Daniel Shahaf
2021-04-07 14:28 ` Marlon
2021-04-07 15:14   ` Daniel Shahaf
2021-04-07 16:36   ` Bart Schaefer
2021-04-07 18:15   ` Mikael Magnusson
2021-04-07 18:50     ` Daniel Shahaf
2021-04-07 20:08     ` Arseny Maslennikov
2021-04-09 20:07     ` Marlon
2021-04-09 22:04       ` Oliver Kiddle
2021-04-09 23:04         ` Daniel Shahaf
2021-04-09 23:55           ` Bart Schaefer
2021-04-13 15:00             ` Daniel Shahaf
2021-04-09 23:08         ` Bart Schaefer
2021-04-10  7:44           ` Roman Perepelitsa
2021-04-09 23:23       ` Mikael Magnusson
2021-04-10  7:45         ` Marlon Richert
2021-04-09 15:29   ` Marlon

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=15283D59-F7B5-4A4C-AFFA-B9D3BB46963F@gmail.com \
    --to=marlon.richert@gmail.com \
    --cc=arseny@altlinux.org \
    --cc=d.s@daniel.shahaf.name \
    --cc=idoenmez@suse.de \
    --cc=kdudka@redhat.com \
    --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).