zsh-users
 help / color / mirror / code / Atom feed
From: Juhapekka Tolvanen <juhtolv@st.jyu.fi>
To: zsh-users mailing list <zsh-users@sunsite.auc.dk>
Subject: [schaefer@candle.brasslantern.com: Re: How to exploit chpwd-function?]
Date: Fri, 20 Apr 2001 01:27:25 +0300	[thread overview]
Message-ID: <20010420012725.A4486@silmu.st.jyu.fi> (raw)

Bart forgot to send his answer to this list, too:

Anyway, those ways to exploit chpwd sounds so cool that I think I'll
add some stuff of that kind to my shell-configs some day.

----- Forwarded message from Bart Schaefer <schaefer@candle.brasslantern.com> -----

From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
Message-Id: <1010419025502.ZM8775@candle.brasslantern.com>
Date: Thu, 19 Apr 2001 02:55:01 +0000
In-Reply-To: <20010418192521.A20505@silmu.st.jyu.fi>
References: <20010418192521.A20505@silmu.st.jyu.fi>
To: Juhapekka Tolvanen <juhtolv@st.jyu.fi>
Subject: Re: How to exploit chpwd-function?
Content-Length: 1349
Lines: 34

On Apr 18,  7:25pm, Juhapekka Tolvanen wrote:
} Subject: How to exploit chpwd-function?
}
} Need I say more? Would you please tell me your favourite ways to use
} chpwd-function.
} 
} P.S: I do not subscribe to this list, but I am smart enough to read
} mailing-list archives via WWW. You can Cc: to me, if I want.

A search on chpwd in the zsh-users archive gives 73 hits, covering only
three topics (aside from bug reports):

    using chpwd to set the xterm title (and similar stunts) [better done
    with precmd, but see also the zftp_chpwd function in the 3.1.9 and
    later zsh manual]; 

    using chpwd to save and load a per-directory zsh history;

    using chpwd to report whether the new $PWD is a symlink.

A search on zsh-workers turns up nothing else of interest.

In the past, I've used chpwd to check whether the .exrc file in the current
directory could safely be read and set EXINIT accordingly; but as I now use
emacs more often than vi, I've dropped that.

The only thing left in my chpwd function now is assigning cwd=$PWD, because
I first learned csh and still occasionally type $cwd by "mistake."

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


----- End forwarded message -----

-- 
Juhapekka "naula" Tolvanen * U of Jyväskylä * * juhtolv@st.jyu.fi
http://www.st.jyu.fi/~juhtolv/spam.html * STRAIGHT BUT NOT NARROW
-----------------------------------------------------------------
"There's a new game we like to play, you see, a game with added
reality. You treat me like a dog. Get me down on my knees. We
call it 'Master and servant'."                       Depeche Mode


                 reply	other threads:[~2001-04-19 22:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010420012725.A4486@silmu.st.jyu.fi \
    --to=juhtolv@st.jyu.fi \
    --cc=zsh-users@sunsite.auc.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).