public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: David Sastre Medina <d.sastre.medina@gmail.com>
To: cygwin@cygwin.com
Subject: Re: /etc/profile
Date: Wed, 22 Aug 2012 22:08:00 -0000	[thread overview]
Message-ID: <20120822205507.GA23279@pris.crapsteak.org> (raw)
In-Reply-To: <50353D71.9000306@dancol.org>

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

On Wed, Aug 22, 2012 at 01:13:37PM -0700, Daniel Colascione wrote:
> On 8/22/12 12:10 PM, David Sastre Medina wrote:
> > On Tue, Aug 21, 2012 at 10:16:28AM +0000, Achim Gratz wrote:
> >> I'm removing the Windows PATH in my startup scripts since there's nothing in
> >> there that I think should be accessible from Cygwin.
> > 
> > All three changes will be available in the next release (profile_d
> > modification taken from your last version in this thread).
> 
> Are you sure that's actually a good idea? I don't agree with this logic:
> People execute Windows programs using Cygwin all the time. With this
> change, basic things like "cmd" and "notepad" will fail to work.
> Working with Windows programs is the *point* of Cygwin. I really don't
> think this change should go into the default startup scripts.

I for one never start windows programs from within a shell, with the
exception of firefox, and for that I registered an entry in the
alternatives system (x-www-browser), however, I take your advice and
I'll give this a second thought, and also would like to hear from
others' opnion wrt to this.
Obviously, ORIGINAL_PATH (as proposed in Achim's patch) would
still hold the native Windows' PATH, so it'd be very easy to include a
(commented?) line using it, so it would be easy to switch it:

#PATH="/usr/local/bin:/usr/bin:${ORIGINAL_PATH}"

-- 
Primary key fingerprint: AD8F BDC0 5A2C FD5F A179  60E7 F79B AB04 5299 EC56

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

  parent reply	other threads:[~2012-08-22 20:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-21 15:03 /etc/profile Achim Gratz
2012-08-21 15:35 ` /etc/profile Eric Blake
2012-08-21 15:57   ` /etc/profile Achim Gratz
2012-08-21 16:11     ` /etc/profile James Johnston
2012-08-21 16:50     ` /etc/profile Eric Blake
2012-08-21 17:21       ` /etc/profile Achim Gratz
2012-08-21 19:27         ` /etc/profile Eric Blake
2012-08-21 20:48           ` /etc/profile Achim Gratz
2012-08-21 17:24     ` /etc/profile Earnie Boyd
2012-08-22 19:42 ` /etc/profile David Sastre Medina
2012-08-22 20:10   ` /etc/profile Achim Gratz
2012-08-22 20:15     ` /etc/profile David Sastre Medina
2012-08-22 20:50       ` /etc/profile Achim Gratz
2012-08-25 15:45       ` /etc/profile Achim Gratz
2012-08-25 21:26         ` /etc/profile Achim Gratz
2012-08-22 20:36   ` /etc/profile Daniel Colascione
2012-08-22 20:51     ` /etc/profile Achim Gratz
2012-08-22 20:55       ` /etc/profile Christopher Faylor
2012-08-22 21:18         ` /etc/profile Achim Gratz
2012-08-23  6:35           ` /etc/profile Andrew DeFaria
2012-08-22 20:55       ` /etc/profile Andrey Repin
2012-08-22 22:52         ` /etc/profile Achim Gratz
2012-08-22 22:08     ` David Sastre Medina [this message]
2012-08-23  5:54       ` /etc/profile Christopher Faylor
2012-08-23  6:19         ` /etc/profile David Sastre Medina
2012-08-23 10:03         ` /etc/profile Achim Gratz
2012-08-23 10:29           ` /etc/profile L Anderson

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=20120822205507.GA23279@pris.crapsteak.org \
    --to=d.sastre.medina@gmail.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).