zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: Rewrite of zsh-newuser-install (Mikael's subthread)
Date: Tue, 13 Apr 2021 14:55:03 +0000	[thread overview]
Message-ID: <20210413145503.GN6819@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <A6A66D59-5043-46C1-B3AB-05279CB895E1@dana.is>

dana wrote on Sat, Apr 10, 2021 at 15:46:57 -0500:
> Aside from being busy, i've kind of stepped back from this project because
> i've started to have some anxiety about it myself. Although i still feel we
> can't be *too* minimalistic with a default config, since nobody would use it,
> the proposed changes have gone beyond the scope i'd initially envisioned. At
> the same time, i don't know how to make an 'objective' case for why x change
> is desirable but y change is excessive.

Why need it be objective?  If there's consensus on this list that
something should be added, add it; else, leave it out.  That's a high
bar, so it'll keep the result conservative/minimal.

> That ties in with another concern i have, which is that once a user installs
> this configuration, it's basically untouchable to us. We can't really patch it
> after the fact if there's a problem with it. The more complex the config is,
> the greater the risk that we'll have an issue like that.
> 
> Those two observations lead me to feel that, if we do go forward with this,
> maybe implementing it with prompt styles and auto-loaded functions would be
> the way to go after all. That would hide some of the more overwhelming aspects
> of the config from end users, and it would allow us to patch bugs or otherwise
> improve things after the fact.
> 

We could have, say, an autoloaded function called zsh-defaults, and have
the default zshrc consist of a (possibly commented-out) call to that
function.  That's similar to what Vim does nowadays, with
a «defaults.vim» runtime file that people can choose to source.

Cheers,

Daniel


  parent reply	other threads:[~2021-04-13 14:55 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
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 [this message]
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=20210413145503.GN6819@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).