From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14603 invoked by alias); 21 Mar 2013 12:06:18 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 17728 Received: (qmail 108 invoked from network); 21 Mar 2013 12:06:13 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,RCVD_IN_DNSWL_LOW, T_DKIM_INVALID autolearn=no version=3.3.2 Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.223.178 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=gNcb+maQXZmB9xmhOJiQVp19l2xMPYRhqTPLNgJJFU4=; b=EIyHBAaLQOhWRn58co+pYzoJEP081gjHEoiKP8QaKo9Apx4RNp5Kzc1ayiBVG3oPRD 0Wfs5Wm3vmdrMpqs/4YZuD7SPYKV/re6/Q/7G2j6o86AbdlyJfxAt7wpOsAb+rWUkxQy a7M+tM8QdaGM9unxX6mjdfj2tksngR7p04SpGPe7KRnlB5XJ/sq1HCiy3HMUV3WnLK3p JQ81vATmGehNBgb4ijgl0mcBsKOSM7fHfiffk+0IqdPo3jH2R26hijIQjgidYAvlaHYa U/Hng5j0FjtF4xmyCQjMFv+r9CkSdBuFF55EfNEe1im3QD2urDjY9Nh+vp6Z0hexlw5q qa1w== X-Received: by 10.50.131.195 with SMTP id oo3mr1974853igb.22.1363867567072; Thu, 21 Mar 2013 05:06:07 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <130320224152.ZM22924@torch.brasslantern.com> References: <130320224152.ZM22924@torch.brasslantern.com> From: Richard Hartmann Date: Thu, 21 Mar 2013 13:05:47 +0100 Message-ID: Subject: Re: Please implement auto-handling of ${HOME}/.zsh/ To: Bart Schaefer Cc: "zsh-users@zsh.org" Content-Type: text/plain; charset=UTF-8 On Thu, Mar 21, 2013 at 6:41 AM, Bart Schaefer wrote: > Like TJ, I have a common set of config files stored on the web. (Not > in Dropbox, in a source repository from which I check out to ~/.zsh, > but it's the same idea.) One of the files in that repository is a > script called ".installer" which writes something much like the above > into ~/.zshenv (with a warning if that would clobber an existing file, > etc.). I haven't yet needed to, but I've considered having .installer > also write bash init files that exec zsh if zsh is not in /etc/shells. This is a tad off topic, but vcsh[1] does exist and deals with this issue nicely without the need for installer scripts. Your zsh, and other, configs is then a simple `vcsh clone` away which is basically a wrapper around git, forcing it to put several working copies into $HOME along each other. Richard [1] https://github.com/RichiH/vcsh