From: Jonas Kramer <jkramer@nex.scrapping.cc>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: Seg. Fault when calling "cd" with set "chpwd" hook from a widget
Date: Sun, 30 Nov 2008 11:59:31 +0100 [thread overview]
Message-ID: <20081130105931.GA29769@unknown> (raw)
In-Reply-To: <081129203135.ZM6271@torch.brasslantern.com>
[-- Attachment #1: Type: text/plain, Size: 1534 bytes --]
On Sat, Nov 29, 2008 at 08:31:35PM -0800, Bart Schaefer wrote:
> On Nov 25, 1:05am, Jonas Kramer wrote:
> >
> > # Control + B jumps to "base" directory.
> > function return-to-base; {
>
> Not directly pertinent, but what's the semicolon for?
Now that you ask, I don't know. I guess I'm just used to it.
>
> > function chpwd; {
> > DIRECTORY="$PWD"
> > while true; do
> > if [ -f './.env.rc' ]; then
> > source './.env.rc'
> > break
> > fi
> > if [ -f './env' ]; then
> > source './env'
> > break
> > fi
> > [ $PWD = '/' ] && break
> > cd -q ..
> > done
> > cd -q "$DIRECTORY"
> > }
> >
> > Now when BASE points to a directory that contains a .env.rc file and I
> > press ^B, it seems to work fine at first, the directory is updated and I
> > get a new nice prompt. But then, no matter what I enter, after hitting
> > return zsh crashes with a seg. fault. This seems to happen in
> > hist.c:1138, where hptr points to NULL at that point.
>
> Are there any commands in ./.env.rc or ./env that manipulate the history?
I don't know if commands executed in a chpwd hook function are added to
the history (they shouldn't in my oppinion), but I'm not explicitly
changing it in there. This is a sample .env.rc I'm using in a project:
# vim:filetype=zsh
export BASE=$PWD
export PERL5LIB="$PWD/code/"
/usr/bin/ctags --languages="Perl" -R "$PWD"
Regards,
Jonas
--
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2008-11-30 11:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 0:05 Jonas Kramer
2008-11-25 18:36 ` Peter Stephenson
2008-11-25 18:40 ` Peter Stephenson
2008-11-30 4:31 ` Bart Schaefer
2008-11-30 10:59 ` Jonas Kramer [this message]
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=20081130105931.GA29769@unknown \
--to=jkramer@nex.scrapping.cc \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/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).