public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: /bin/pwd versus built-in pwd
Date: Wed, 17 Jan 2001 12:43:00 -0000	[thread overview]
Message-ID: <20010117154318.D14952@redhat.com> (raw)
In-Reply-To: <200101172009.WAA11316@linux.>

On Wed, Jan 17, 2001 at 10:09:06PM +0200, Ehud Karni wrote:
>On Tue, 16 Jan 2001 14:56:23 -0800, Bob McGowan <rmcgowan@veritas.com> wrote:
>> 
>>  "...That is, all components of the printed name will be actual
>>   directory names -- none will be symbolic links."
>> 
>> I'd say this is a bug.
>
>Despite what Christopher Faylor <cgf@redhat.com> thinks, I'll say it
>is a real bug with critical implications.

Huh?  I never said it wasn't a bug.  Quite the contrary.

I suggested that people read the email archives.  Look for "pwd symlink".

>If you want to check if directories are the same, or in the same branch
>absolute paths must be used.  I have many scripts (all of them working
>on Linux and other UNIX's) that use `/bin/pwd` to get the absolute
>path.  If the current situation is kept (i.e.  `/bin/pwd` returning the
>path the shell used to get to this directory, not the absolute one)
>then it is a big immigration problem.

I have no idea what an "immigration problem" is but you're welcome, as
always to submit a patch.

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2001-01-17 12:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-16 13:46 Fred Kulack
2001-01-16 15:03 ` Bob McGowan
2001-01-16 17:04   ` Christopher Faylor
2001-01-16 17:37     ` Bob McGowan
2001-01-17 12:09   ` Ehud Karni
2001-01-17 12:43     ` Christopher Faylor [this message]
2001-01-27  7:47       ` Christopher Faylor
2001-01-17  7:26 Fred Kulack
2001-01-18  0:28 Bernard Dautrevaux
2001-01-18  7:34 ` Ehud Karni
2001-01-18 13:52   ` Christopher Faylor
2001-01-18  9:38 Bernard Dautrevaux

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=20010117154318.D14952@redhat.com \
    --to=cgf@redhat.com \
    --cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).