Date: Mon, 29 Jan 2007 22:43:28 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: freebsd-questions@freebsd.org Subject: Re: stupid scripting question: zsh Message-ID: <20070130044328.GA19656@dan.emsphone.com> In-Reply-To: <20070130011246.GB52136@parts-unknown.org> References: <20070129223730.GA7986@parts-unknown.org> <20070129231940.GD78513@dan.emsphone.com> <20070130011246.GB52136@parts-unknown.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jan 29), David Benfell said: > On Mon, 29 Jan 2007 17:19:40 -0600, Dan Nelson wrote: > > In the last episode (Jan 29), David Benfell said: > > > I've been upgrading my FreeBSD system into a fully-fledged > > > desktop system. > > > > > > zsh as installed (from the port) seems only to recognize the > > > /etc/zshenv startup file. And I needed an stty command to get > > > proper backspace/delete behavior. Because only the /etc/zshenv > > > file seemed to be recognized, I had to put the stty command in > > > it. > > > > I'd start by figuring out why the other zsh startup scripts aren't > > being read. I install zsh from ports on all my systems and haven't > > seen this. Are you running zsh -f, or have you unset the RCS shell > > option from within zshenv? Either will prevent the other rc > > scripts from being loaded. If you run "truss -f -o log zsh", do > > you see it try to load zshrc? > > Okay, I figured out how to run truss (yes, I had the PROCFS and > PSEUDOFS options in my kernel). Yes, it tries to access /etc/zshrc. > I was trying zlogin, which I had seen on a Linux system. zlogin should be also read, but only on login shells. For testing purposes, you can force a login shell after you've logged in by running "zsh -l". -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070130044328.GA19656>