public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Bob McGowan <rmcgowan@veritas.com>
To: "David A. Cobb" <superbiskit@home.com>
Cc: cygwin@sources.redhat.com
Subject: Re: Current Directory? [Branch from Re: DLL naming conventions]
Date: Tue, 05 Sep 2000 15:02:00 -0000	[thread overview]
Message-ID: <39B56E80.38BF932C@veritas.com> (raw)
In-Reply-To: <39B5597B.779582AF@home.com>

"David A. Cobb" wrote:
> 
> Bob McGowan wrote:
> 
> > I'd like to expand on this, hopefully to add clarity.  The above is
---
The one thing I did not say I was doing, was looking at this from a
"command line" orientation.  Windowing software adds complexity since
the user now is seeing multiple instances of applications.

> 
> The "Current Directory" then, must be a property/attribute of the "Current
> Process."  Is that correct?  With respect to the operator, it is relative
> to the current top window?

I'm not sure what the definition should be for "Current Process".  If by
that you mean the currently active, top window, then basically, yes. 
But, each and every process has a "current directory", whether or not it
is currently running, whether or not it is the "top window", etc.  You
are correct that from the perspective of the operator, the operator's
"current directory" will be that of the top window.

> In other words, when I launch a program the cd is established by the
> [shell] process in which I execute the launch command.  Subsequently, the
> running
> process may change it internally.  If I focus somewhere else, "my" current
> directory changes, but that's irrelevant to the program I launched before.
> 
> Have I got it?
> 

I think you've got it ;)

-- 
Bob McGowan
Staff Software Quality Engineer
VERITAS Software
rmcgowan@veritas.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

  reply	other threads:[~2000-09-05 15:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-01  4:49 DLL naming conventions Tor Lillqvist
2000-09-01  6:47 ` Charles S. Wilson
2000-09-02  6:56   ` Gary V. Vaughan
2000-09-02 11:36     ` Charles S. Wilson
2000-09-02 16:40       ` Gary V. Vaughan
2000-09-02 19:20         ` Chris Faylor
2000-09-02 21:23           ` Robert Collins
2000-09-02 22:56           ` Charles Wilson
2000-09-03  5:31           ` Gary V. Vaughan
2000-09-03  9:31             ` Chris Faylor
2000-09-03 10:32               ` Chris Faylor
2000-09-04  6:56               ` Gary V. Vaughan
2000-09-04 15:22           ` Current Directory? [Branch from Re: DLL naming conventions] David A. Cobb
2000-09-04 19:53             ` Chris Faylor
2000-09-05 12:29               ` Bob McGowan
2000-09-05 13:37                 ` David A. Cobb
2000-09-05 15:02                   ` Bob McGowan [this message]
2000-09-02 22:32         ` DLL naming conventions Charles Wilson
2000-09-03  5:29           ` Gary V. Vaughan
2000-09-03 12:40             ` Alexandre Oliva

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=39B56E80.38BF932C@veritas.com \
    --to=rmcgowan@veritas.com \
    --cc=cygwin@sources.redhat.com \
    --cc=superbiskit@home.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).