zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: dana <dana@dana.is>
Cc: Marlon <marlon.richert@gmail.com>,
	Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Rewrite of zsh-newuser-install (Mikael's subthread)
Date: Sat, 10 Apr 2021 14:41:41 -0700	[thread overview]
Message-ID: <CAH+w=7a4i1ozOFcLbqFdPm7=XTv08hEp_NvsQ9-HgakkQn=MWQ@mail.gmail.com> (raw)
In-Reply-To: <A6A66D59-5043-46C1-B3AB-05279CB895E1@dana.is>

On Sat, Apr 10, 2021 at 1:47 PM dana <dana@dana.is> wrote:
>
> the proposed changes have gone beyond the scope i'd initially envisioned.

Ditto.

> the proposed configuration is too complex to be of much help with
> the stated goal of demonstrating how new users can modify their own config.

This is also my feeling.

> 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.

Not if the user is encouraged to edit it in place, anyway.

> 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.

This is venturing into the territory of "should zsh ship with a
preferred module management system"?  Because we're demonstrating a
use case for modules, here, which we haven't previously had any need
for.  If everything we want CAN be done with autoloaded functions, of
course, that's as "modular" as we need to get.

> I feel silly for bringing up fundamental 'architecture' questions so late in
> the game

It wasn't clear, early on, that the scope of the changes would require
architecting.


  reply	other threads:[~2021-04-10 21:42 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 [this message]
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='CAH+w=7a4i1ozOFcLbqFdPm7=XTv08hEp_NvsQ9-HgakkQn=MWQ@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=dana@dana.is \
    --cc=marlon.richert@gmail.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).