From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17956 invoked by alias); 11 Oct 2014 22:00:48 -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: 19238 Received: (qmail 20700 invoked from network); 11 Oct 2014 22:00:46 -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.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 From: Bart Schaefer Message-id: <141011150111.ZM28417@torch.brasslantern.com> Date: Sat, 11 Oct 2014 15:01:11 -0700 In-reply-to: <5439A54A.9060304@eastlink.ca> Comments: In reply to Ray Andrews "Re: zsh 5.0.7" (Oct 11, 2:46pm) References: <54397CC0.9070206@eastlink.ca> <141011131053.ZM28143@torch.brasslantern.com> <5439A54A.9060304@eastlink.ca> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-users@zsh.org Subject: Re: zsh 5.0.7 MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Oct 11, 2:46pm, Ray Andrews wrote: } } Ok, so what's the approved fix? In this particular install I have no } need to keep anything around that's not current, and of course I want } all roads to lead to 5.0.7. Should I just fiddle with the pointers? You have several choices. Firstly, you need to see if chsh will let you set your login shell to /usr/local/bin/zsh. If it won't, you can either -- 1. find out which path actually is your login shell and link that path to /usr/local/bin/zsh, or (if that would fluster your upgrades) 2. try editing the file /etc/shells to add /usr/local/bin/zsh and then run chsh again, or 3. set up your login shell init to "exec /usr/local/bin/zsh" in the appropriate circumstances. See FAQ "I don't have root access: how do I make zsh my login shell?" for discussion of that last. Once you get zsh going as your login shell, you need to change the order of directories in the $path array to put /usr/local/bin near the front. If you can't do that for some other reason, you're back to option (1) above. You can also try to use your package manager to find out what installed /usr/bin/zsh{,5} and remove that package. Once you have done so, you can rerun configure in your zsh build to set --exec-prefix=/usr and then rebuild and install, but it'd probably be wiser to get it running out of /usr/local if you can.