public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: "Øystein Walle" <oystwa@gmail•com>
Cc: git@vger•kernel.org, Brandon Turner <bt@brandonturner•net>
Subject: Re: [PATCH v3] completion: ignore chpwd_functions when cding on zsh
Date: Thu, 09 Oct 2014 11:10:44 -0700	[thread overview]
Message-ID: <xmqqlhop6rmj.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <loom.20141009T093007-811@post.gmane.org> ("Øystein Walle"'s message of "Thu, 9 Oct 2014 07:34:30 +0000 (UTC)")

Øystein Walle <oystwa@gmail•com> writes:

> Brandon Turner <bt <at> brandonturner.net> writes:
>
>> 
>> Software, such as RVM (ruby version manager), may set chpwd functions
>> that result in an endless loop when cding.  chpwd functions should be
>> ignored.
>
> Now that it has moved to the zsh-specific script you can achieve this more
> simply by using cd -q.

;-)

Is the way we defeat CDPATH for POSIX shells sufficient, or does it
also need to be customized for zsh?

  reply	other threads:[~2014-10-09 18:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-08  3:53 [PATCH] completion: ignore chpwd_functions when cding Brandon Turner
2014-10-08 18:12 ` Junio C Hamano
2014-10-08 21:49   ` [PATCH v2] " Brandon Turner
2014-10-08 21:49   ` [PATCH v3] completion: ignore chpwd_functions when cding on zsh Brandon Turner
2014-10-09  7:34     ` Øystein Walle
2014-10-09 18:10       ` Junio C Hamano [this message]
2014-10-09 19:01         ` [PATCH v4] " Brandon Turner
2014-10-09 19:47           ` Øystein Walle
2014-10-09 20:01             ` Junio C Hamano
2014-10-09 20:45           ` Junio C Hamano
2014-10-09 22:04             ` Brandon Turner
2014-10-09 22:11               ` Junio C Hamano
2014-10-09 22:30                 ` Brandon Turner
2014-10-16 18:10                   ` Øystein Walle
2014-10-09 19:21         ` [PATCH v3] " Øystein Walle
2014-10-08 21:50   ` [PATCH] completion: ignore chpwd_functions when cding Brandon Turner

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=xmqqlhop6rmj.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=bt@brandonturner$(echo .)net \
    --cc=git@vger$(echo .)kernel.org \
    --cc=oystwa@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox