cygwin.bat

cygwin.bat

[Alex Malinovich]

Just a quick observation. Cygwin.bat calls "bash --login -i" to start
cygwin. Wouldn't it be a bit better to instead use 'start' to launch
bash?

e.g.

"start bash --login -i" 

By using 'start' bash is called, and then the batchfile continues
execution. (it ends)

This would alleviate the issue of "Terminate batch job?" messages that
occasionally crop up when closing the window. It also allows more than
one instance of bash to be called by using a keyboard shortcut. I have
ctrl-alt-c set to call cygwin.bat. The only problem is that if I already
have a window open, it won't allow me to open a second one that way
since the batch file is still "running". Using 'start', I can now open
as many windows as I want. AFAIK the 'start' command has been
implemented in all MS OS's since 95 so compatibility shouldn't be an
issue. Just a suggestion.

-Alex


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

cygwin.bat

[123cu]

First, I am a newbee to Cygwin so please excuse my lack of knowledge.

I have a text file (aaa.txt) which contains a simple grep command. When I
start Cygwin.bat, I want this file to be started (executed) as part of
invoking the cygwin.bat file. I don't know how to do it. Any help will be
appreciated.

cygwin.bat file
@echo on

C:
chdir C:\cygwin\bin
set HOME=\cygwin
bash --login -i
-- 
View this message in context: http://www.nabble.com/cygwin.bat-tf4837351.html#a13839178
Sent from the Cygwin list mailing list archive at Nabble.com.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin.bat

[Brian Mathis]

On Nov 19, 2007 11:01 AM, 123cu <fmk0203@charter.net> wrote:
>
> First, I am a newbee to Cygwin so please excuse my lack of knowledge.
>
> I have a text file (aaa.txt) which contains a simple grep command. When I
> start Cygwin.bat, I want this file to be started (executed) as part of
> invoking the cygwin.bat file. I don't know how to do it. Any help will be
> appreciated.
>
> cygwin.bat file
> @echo on
>
> C:
> chdir C:\cygwin\bin
> set HOME=\cygwin
> bash --login -i

cygwin.bat is typically used to start the cygwin environment, usually
by starting a bash shell.  The bash shell then runs some "startup"
scripts, like .bashrc and .bash_profile.  Those files are where you
would normally put anything that you want to run every time you start
a shell.

Based on your description, it sounds like you may be doing something
that might not fit with the idea of how cygwin works.  If you can
explain in more detail what you are trying to accomplish, we may be
able to find a better solution, or help you to integrate it better.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin.bat

[Carlo Florendo]

123cu wrote:
> First, I am a newbee to Cygwin so please excuse my lack of knowledge.
> 
> I have a text file (aaa.txt) which contains a simple grep command. When I
> start Cygwin.bat, I want this file to be started (executed) as part of
> invoking the cygwin.bat file. I don't know how to do it. Any help will be
> appreciated.
> 
> cygwin.bat file
> @echo on
> 
> C:
> chdir C:\cygwin\bin
> set HOME=\cygwin
> bash --login -i

I could give you two ways to do that:

1) You simply have to edit /etc/bash.bashrc then add the line that executes 
aaa.txt.  For example, if, as you say, your file aaa.txt is in "c:\temp 
dir" and contains a *simple* grep command, then the line on the 
/etc/bash.bashrc file would look like this:

`cat /cygdrive/c/temp\ dir/aaa.txt`

Note the backticks at the start and end of the line and note that the 
directory appears as:

"temp\ dir"

and not

"temp dir"



2) You could actually put the entire grep command on /etc/bash.bashrc if 
you wish.


Thank you very much!

Best Regards,

Carlo

-- 
Carlo Florendo
Music Research and Development Division
Astra Philippines Inc.
UP-Ayala Technopark, UP Campus Diliman
1101 Quezon City, Philippines
http://www.astra.ph

--
The Astra Group of Companies
5-3-11 Sekido, Tama City
Tokyo 206-0011, Japan
http://www.astra.co.jp

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

cygwin.bat

[derek]

Anyone actually find that thing useful?
I removed it because I was tired of CTRL-C getting intercepted when I
closed a window.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin.bat

[Igor Pechtchanski]

On Fri, 9 May 2003, derek wrote:

> Anyone actually find that thing useful?

Sure.  I do.  Use it all the time on Win2k.

> I removed it because I was tired of CTRL-C getting intercepted when I
> closed a window.

WAG: read up on the "tty" setting in the CYGWIN environment variable
(<http://cygwin.com/cygwin-ug-net/using-cygwinenv.html>).
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Knowledge is an unending adventure at the edge of uncertainty.
  -- Leto II


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin.bat

[derek]

Igor Pechtchanski wrote:

>On Fri, 9 May 2003, derek wrote:
>
>  
>
>>Anyone actually find that thing useful?
>>    
>>
>
>Sure.  I do.  Use it all the time on Win2k.
>
>  
>
>>I removed it because I was tired of CTRL-C getting intercepted when I
>>closed a window.
>>    
>>
>
>WAG: read up on the "tty" setting in the CYGWIN environment variable
>(<http://cygwin.com/cygwin-ug-net/using-cygwinenv.html>).
>	Igor
>  
>
I've looked into that in the past. As far as I can remember, all that
can be done is disabling ctrl-c entirely - not that the link was much help.
Since pretty much everything can be set outside of cygwin.bat, it just
seems like an annoyance.  Could be my imagination, but even seems a
little slower.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin.bat

[Larry Hall (RFK Partners, Inc.)]

derek wrote:
> Igor Pechtchanski wrote:
> 
> 
>>On Fri, 9 May 2003, derek wrote:
>>
>> 
>>
>>
>>>Anyone actually find that thing useful?
>>>   
>>>
>>
>>Sure.  I do.  Use it all the time on Win2k.
>>
>> 
>>
>>
>>>I removed it because I was tired of CTRL-C getting intercepted when I
>>>closed a window.
>>>   
>>>
>>
>>WAG: read up on the "tty" setting in the CYGWIN environment variable
>>(<http://cygwin.com/cygwin-ug-net/using-cygwinenv.html>).
>>	Igor
>> 
>>
> 
> I've looked into that in the past. As far as I can remember, all that
> can be done is disabling ctrl-c entirely - not that the link was much help.


That may have been your experience but it doesn't represent the intent
and capabililty of the 'tty' setting for the CYGWIN environment variable.
See <http://cygwin.com/cygwin-ug-net/using-cygwinenv.html> for more
definitive information on it's capabilities and usage.


> Since pretty much everything can be set outside of cygwin.bat, it just
> seems like an annoyance.  


Ah good.  So it's working as planned! ;-)

Seriously, you're not *required* to use it.


>Could be my imagination, but even seems a
> little slower.


That *would* be your imagination.


-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin.bat

[Sam Edge]

"Larry Hall (RFK Partners, Inc.)" <lhall@rfk.com> wrote in
<3EBC793B.9000301@rfk.com>
in gmane.os.cygwin on Fri, 09 May 2003 23:59:55 -0400:

> >Could be my imagination, but even seems a
> > little slower.

> That *would* be your imagination.

Maybe not.

If you start up bash.exe directly by double-clicking it or by putting
bash.exe in a shortcut, then only one process is created.

If you use cygwin.bat, then under Windows NT/2k/XP you first have a
CMD.EXE process created and then a bash.exe. The CMD.EXE sits around
doing nothing until the bash.exe process exits.

It will therefore take longer to get from the initial double-click to
the cursor flashing at the bash prompt. On a slower PC this may be a
discernable extra delay.

The extra CME.EXE also uses system resources (virtual memory, kernel
objects, etc.) and will therefore slow all other processes down by a
very small amount, although I doubt whether this effect would be
noticeable unless the PC was already heavily over-committed.


-- 
Sam Edge

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin.bat

[Christopher Faylor]

On Sat, May 10, 2003 at 09:04:28PM +0100, Sam Edge wrote:
>"Larry Hall (RFK Partners, Inc.)" <lhall@rfk.com> wrote in
><3EBC793B.9000301@rfk.com>
>in gmane.os.cygwin on Fri, 09 May 2003 23:59:55 -0400:
>
>> >Could be my imagination, but even seems a
>> > little slower.
>
>> That *would* be your imagination.
>
>Maybe not.
>
>If you start up bash.exe directly by double-clicking it or by putting
>bash.exe in a shortcut, then only one process is created.
>
>If you use cygwin.bat, then under Windows NT/2k/XP you first have a
>CMD.EXE process created and then a bash.exe. The CMD.EXE sits around
>doing nothing until the bash.exe process exits.
>
>It will therefore take longer to get from the initial double-click to
>the cursor flashing at the bash prompt. On a slower PC this may be a
>discernable extra delay.
>
>The extra CME.EXE also uses system resources (virtual memory, kernel
>objects, etc.) and will therefore slow all other processes down by a
>very small amount, although I doubt whether this effect would be
>noticeable unless the PC was already heavily over-committed.

Translation: Except for a neglible startup cost, it's probably his
imagination.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin.bat

[Sam Edge]

cjf wrote in <20030511002234.GD17951@redhat.com>
in gmane.os.cygwin on Sat, 10 May 2003 20:22:34 -0400:

> >> >Could be my imagination, but even seems a
> >> > little slower.
> >> That *would* be your imagination.

> >Maybe not.
> >If you start up bash.exe directly by double-clicking it or by putting
> >bash.exe in a shortcut, then only one process is created.
> >
> >If you use cygwin.bat, then under Windows NT/2k/XP you first have a
> >CMD.EXE process created and then a bash.exe. The CMD.EXE sits around
> >doing nothing until the bash.exe process exits.
> > [snip]

> Translation: Except for a neglible startup cost, it's probably his
> imagination.

Negligible on a modern PC. Noticeable on some of the kit I've got
here. ;-)


-- 
Sam Edge
(who seldom parts with a working computer)

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin.bat

[Christopher Faylor]

On Sun, May 11, 2003 at 03:11:30AM +0100, Sam Edge wrote:
>cjf wrote in <20030511002234.GD17951@redhat.com>
>in gmane.os.cygwin on Sat, 10 May 2003 20:22:34 -0400:
>
>> >> >Could be my imagination, but even seems a
>> >> > little slower.
>> >> That *would* be your imagination.
>
>> >Maybe not.
>> >If you start up bash.exe directly by double-clicking it or by putting
>> >bash.exe in a shortcut, then only one process is created.
>> >
>> >If you use cygwin.bat, then under Windows NT/2k/XP you first have a
>> >CMD.EXE process created and then a bash.exe. The CMD.EXE sits around
>> >doing nothing until the bash.exe process exits.
>> > [snip]
>
>> Translation: Except for a neglible startup cost, it's probably his
>> imagination.
>
>Negligible on a modern PC. Noticeable on some of the kit I've got
>here. ;-)

I *really* find that hard to believe.  I've run cygwin on some pretty
slow computers and I've never noticed a slowdown from running bash
in a command shell.  Even Windows should be smart enough to know that
it can swap out most of command.com when bash.exe is running so I
don't know how this could be a resource thing.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin.bat

[Sam Edge]

cgf wrote in <20030511021835.GB18826@redhat.com>
in gmane.os.cygwin on Sat, 10 May 2003 22:18:35 -0400:

> >> >If you use cygwin.bat, then under Windows NT/2k/XP you first have a
> >> >CMD.EXE process created and then a bash.exe. The CMD.EXE sits around
> >> >doing nothing until the bash.exe process exits.
> >> > [snip]

> >Negligible on a modern PC. Noticeable on some of the kit I've got
> >here. ;-)

> I *really* find that hard to believe.  I've run cygwin on some pretty
> slow computers and I've never noticed a slowdown from running bash
> in a command shell.  Even Windows should be smart enough to know that
> it can swap out most of command.com when bash.exe is running so I
> don't know how this could be a resource thing.

Oh yes. I've already said that the general system slow down due to one
extra waiting process isn't going to be noticeable. (Although just
because a process is swapped out doesn't mean it ceases consuming
resources, especially on Windows!)

But the overhead in /launching/ an extra CMD.EXE to process the ".BAT"
file that then starts up bash.exe can be noticed on old kit under NT.

I suspect that on Win9x the difference is much smaller because,
whether I start bash.exe directly or via cygwin.bat, a WINOA386.MOD
process is always created as well as a BASH.EXE.

-- 
Sam Edge

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: cygwin.bat

[Christopher Faylor]

On Sun, May 11, 2003 at 04:15:05AM +0100, Sam Edge wrote:
>cgf wrote in <20030511021835.GB18826@redhat.com>
>in gmane.os.cygwin on Sat, 10 May 2003 22:18:35 -0400:
>
>> >> >If you use cygwin.bat, then under Windows NT/2k/XP you first have a
>> >> >CMD.EXE process created and then a bash.exe. The CMD.EXE sits around
>> >> >doing nothing until the bash.exe process exits.
>> >> > [snip]
>
>> >Negligible on a modern PC. Noticeable on some of the kit I've got
>> >here. ;-)
>
>> I *really* find that hard to believe.  I've run cygwin on some pretty
>> slow computers and I've never noticed a slowdown from running bash
>> in a command shell.  Even Windows should be smart enough to know that
>> it can swap out most of command.com when bash.exe is running so I
>> don't know how this could be a resource thing.
>
>Oh yes. I've already said that the general system slow down due to one
>extra waiting process isn't going to be noticeable. (Although just
>because a process is swapped out doesn't mean it ceases consuming
>resources, especially on Windows!)

Of course.  It's consuming swap space on disk for one thing.  It's
unlikely that in-use handles or atoms or shared memory is going to have
much impact on active processes however.

>But the overhead in /launching/ an extra CMD.EXE to process the ".BAT"
>file that then starts up bash.exe can be noticed on old kit under NT.

So, once again, as I said:

Translation: Except for a neglible startup cost, it's probably his
imagination.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: cygwin.bat

[Bobby McNulty]

"Alex Malinovich" <baggend@howlermonkey.net> wrote:

>Just a quick observation. Cygwin.bat calls "bash --login -i" to start
>cygwin. Wouldn't it be a bit better to instead use 'start' to launch
>bash?
>
>e.g.
>
>"start bash --login -i" 
>
>By using 'start' bash is called, and then the batchfile continues
>execution. (it ends)
>
>This would alleviate the issue of "Terminate batch job?" messages that
>occasionally crop up when closing the window. It also allows more than
>one instance of bash to be called by using a keyboard shortcut. I have
>ctrl-alt-c set to call cygwin.bat. The only problem is that if I already
>have a window open, it won't allow me to open a second one that way
>since the batch file is still "running". Using 'start', I can now open
>as many windows as I want. AFAIK the 'start' command has been
>implemented in all MS OS's since 95 so compatibility shouldn't be an
>issue. Just a suggestion.
>
>-Alex
>
>
>--
>Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>Bug reporting:         http://cygwin.com/bugs.html
>Documentation:         http://cygwin.com/docs.html
>FAQ:                   http://cygwin.com/faq/
>
>
I just tried it out.

start /r bash --login -i

When exit is sent, the window closes without any fuss.




__________________________________________________________________
Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/

Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: cygwin.bat

[Michael Erdely]

Or, better yet, don't use a batch file at all.  Create an icon that
starts in <drive>:\Path-to-cygwin\bin that launches bash.

Works like a charm.

-ME

-----Original Message-----
From: cygwin-owner@sources.redhat.com
[ mailto:cygwin-owner@sources.redhat.com ] On Behalf Of Bobby McNulty
Sent: Saturday, September 08, 2001 6:27 PM
To: "Alex Malinovich"; cygwin@cygwin.com
Subject: RE: cygwin.bat


"Alex Malinovich" <baggend@howlermonkey.net> wrote:

>Just a quick observation. Cygwin.bat calls "bash --login -i" to start
>cygwin. Wouldn't it be a bit better to instead use 'start' to launch
>bash?
>
>e.g.
>
>"start bash --login -i" 
>
>By using 'start' bash is called, and then the batchfile continues
>execution. (it ends)
>
>This would alleviate the issue of "Terminate batch job?" messages that
>occasionally crop up when closing the window. It also allows more than
>one instance of bash to be called by using a keyboard shortcut. I have
>ctrl-alt-c set to call cygwin.bat. The only problem is that if I
already
>have a window open, it won't allow me to open a second one that way
>since the batch file is still "running". Using 'start', I can now open
>as many windows as I want. AFAIK the 'start' command has been
>implemented in all MS OS's since 95 so compatibility shouldn't be an
>issue. Just a suggestion.
>
>-Alex
>
>
>--
>Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>Bug reporting:         http://cygwin.com/bugs.html
>Documentation:         http://cygwin.com/docs.html
>FAQ:                   http://cygwin.com/faq/
>
>
I just tried it out.

start /r bash --login -i

When exit is sent, the window closes without any fuss.




__________________________________________________________________
Your favorite stores, helpful shopping tools and great gift ideas.
Experience the convenience of buying online with Shop@Netscape!
http://shopnow.netscape.com/

Get your own FREE, personal Netscape Mail account today at
http://webmail.netscape.com/


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: cygwin.bat

[Alex Malinovich]

That's a good idea as well. Thought I get the feeling that it would be
considerably more work to implement than just adding "start" to the
batch file. (From a setup.exe point of view that is.)

-Alex

> -----Original Message-----
> From: cygwin-owner@sources.redhat.com 
> [ mailto:cygwin-owner@sources.redhat.com ] On Behalf Of Michael Erdely
> Sent: Saturday, September 08, 2001 7:56 PM
> To: cygwin@cygwin.com
> Subject: RE: cygwin.bat
> 
> 
> Or, better yet, don't use a batch file at all.  Create an icon that
> starts in <drive>:\Path-to-cygwin\bin that launches bash.
> 
> Works like a charm.
> 
> -ME
> 
> -----Original Message-----
> From: cygwin-owner@sources.redhat.com
> [ mailto:cygwin-owner@sources.redhat.com ] On Behalf Of Bobby McNulty
> Sent: Saturday, September 08, 2001 6:27 PM
> To: "Alex Malinovich"; cygwin@cygwin.com
> Subject: RE: cygwin.bat
> 
> 
> "Alex Malinovich" <baggend@howlermonkey.net> wrote:
> 
> >Just a quick observation. Cygwin.bat calls "bash --login -i" to start
> >cygwin. Wouldn't it be a bit better to instead use 'start' to launch
> >bash?
> >
> >e.g.
> >
> >"start bash --login -i" 
> >
> >By using 'start' bash is called, and then the batchfile continues
> >execution. (it ends)
> >
> >This would alleviate the issue of "Terminate batch job?" 
> messages that
> >occasionally crop up when closing the window. It also allows 
> more than
> >one instance of bash to be called by using a keyboard 
> shortcut. I have
> >ctrl-alt-c set to call cygwin.bat. The only problem is that if I
> already
> >have a window open, it won't allow me to open a second one that way
> >since the batch file is still "running". Using 'start', I 
> can now open
> >as many windows as I want. AFAIK the 'start' command has been
> >implemented in all MS OS's since 95 so compatibility shouldn't be an
> >issue. Just a suggestion.
> >
> >-Alex
> >
> >
> >--
> >Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> >Bug reporting:         http://cygwin.com/bugs.html
> >Documentation:         http://cygwin.com/docs.html
> >FAQ:                   http://cygwin.com/faq/
> >
> >
> I just tried it out.
> 
> start /r bash --login -i
> 
> When exit is sent, the window closes without any fuss.
> 
> 
> 
> 
> __________________________________________________________________
> Your favorite stores, helpful shopping tools and great gift ideas.
> Experience the convenience of buying online with Shop@Netscape!
> http://shopnow.netscape.com/
> 
> Get your own FREE, personal Netscape Mail account today at
> http://webmail.netscape.com/
> 
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 
> 
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 
> 
> 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

cygwin.bat

[Jonas Jensen]

I'm wondering why the Cygwin.bat file is still used for new installations.
It causes problems with CTRL+C and it leaves a cmd.exe waiting in the
background for each Cygwin window opened.
It used to set variables, but they're all set in /etc/profile now, although
some users still appear to have their old Cygwin.bat... which must mean they
get those variables set twice (and that should cause duplications when
prepending to $PATH).

Why not just point the shortcut directly to bash.exe with the neccesary
parameters?

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

Re: cygwin.bat

[DJ Delorie]

> Why not just point the shortcut directly to bash.exe with the neccesary
> parameters?

Patches welcome!

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