public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: lnxg33k <lnxg33k@gmail.com>
Subject: Re: [gentoo-dev] cmake.eclass
Date: Thu, 24 Aug 2006 00:02:21 -0400	[thread overview]
Message-ID: <200608240002.21955.vapier@gentoo.org> (raw)
In-Reply-To: <44ED1BAC.8030806@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 545 bytes --]

On Wednesday 23 August 2006 23:23, lnxg33k wrote:
> Mike Frysinger wrote:
> > use this instead ... makes for cleaner output:
> > pushd "${BUILDDIR}" > /dev/null
>
> Would `cd foo` and `cd -` work just as well in place of `pushd` and `popd`?
> Recent tip I ran across and wondering if it holds up across the board.

'cd -' is generally for interactive shells, pushd/popd is for scripts

plus, while `cd -` is a stack of depth 1, pushd/popd has an infinite stack ... 
so you dont have to worry about recursive calls being wrong
-mike

[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]

      reply	other threads:[~2006-08-24  4:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-18 10:13 [gentoo-dev] cmake.eclass Panard
2006-05-18 10:54 ` Simon Stelling
2006-05-18 11:44   ` Panard
2006-05-24  0:52     ` Mike Frysinger
2006-05-24 10:46       ` Panard
2006-05-24 12:11         ` Thomas Kear
2006-05-24 13:24           ` Panard
2006-05-25 11:31             ` Carsten Lohrke
2006-05-25 14:39               ` Danny van Dyk
2006-05-25 14:37                 ` Diego 'Flameeyes' Pettenò
2006-05-25 14:54                   ` Carsten Lohrke
2006-05-25 22:50               ` Panard
2006-05-25 23:10                 ` Danny van Dyk
2006-05-25 23:09                   ` Diego 'Flameeyes' Pettenò
2006-05-25 23:20                   ` Danny van Dyk
2006-05-25 21:15             ` Mike Frysinger
2006-05-25 22:52               ` Panard
2006-08-24  3:23               ` lnxg33k
2006-08-24  4:02                 ` Mike Frysinger [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=200608240002.21955.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=lnxg33k@gmail.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox