On 10/13/2010 1:58 AM, Autotoonz wrote:
Christopher Faylor-8 wrote:
If you mean that batch file 1 sets the CYGWIN environment variable and
then directly runs batch file 2, then that works too. That's how
environment variables work - once you set an environment variable it is
inherited by all
to suppress the warning on
individual scripts. This now appears to work correctly with CYGWIN, so my
problem seems to have been solved.
Cheers
--
View this message in context:
http://old.nabble.com/nodosfilewarning-not-working-tp29948673p29950134.html
Sent from the Cygwin list mailing list archive
Greetings, Autotoonz!
'setx' can also be invoked from shell scripts but
still only impacts
subsequently invoked shells. In both cases, the results obtain even
after reboot.
Thankyou for this info. Setx will be useful for me in the future because our
Windows PCs are locked down, and I
from now on. I don't need to write my own utility right
now, but thanks for the pointer.
--
View this message in context:
http://old.nabble.com/nodosfilewarning-not-working-tp29948673p29957985.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Problem reports: http
for anyone who wants to block the message for individual scripts, or
(like me) has a locked-down Windoze PC.
Here is the command line I'm running: C:\cygwin\bin\bash --login
C:\test\test.sh
--
View this message in context:
http://old.nabble.com/nodosfilewarning-not-working-tp29948673p29948673.html
On Tue, Oct 12, 2010 at 05:49:31PM -0700, Autotoonz wrote:
Executing scripts with DOS style pathnames causes the following error:
MS-DOS style path detected
CYGWIN environment variable option nodosfilewarning turns off this
warning.
Consult the user's guide for more details about POSIX paths:
On 10/12/2010 8:11 PM, Christopher Faylor wrote:
On Tue, Oct 12, 2010 at 05:49:31PM -0700, Autotoonz wrote:
Executing scripts with DOS style pathnames causes the following error:
MS-DOS style path detected
CYGWIN environment variable option nodosfilewarning turns off this
warning.
Consult
to just do the latter.
As per my original post, this most definitely does *not* work. Have you
tried this yourself yet?
--
View this message in context:
http://old.nabble.com/nodosfilewarning-not-working-tp29948673p29948823.html
Sent from the Cygwin list mailing list archive at Nabble.com
scripts
--
View this message in context:
http://old.nabble.com/nodosfilewarning-not-working-tp29948673p29948847.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation
On Tue, Oct 12, 2010 at 06:24:43PM -0700, Autotoonz wrote:
Christopher Faylor wrote:
It's best to eschew the annoyance and conspiracy theories if you don't
completely understand what's going on and actually want help.
A fair comment, although I'm still puzzled as to how nobody can explain
why
On 10/12/2010 09:24 PM, Autotoonz wrote:
Christopher Faylor-8 wrote:
It's best to eschew the annoyance and conspiracy theories if you don't
completely understand what's going on and actually want help.
A fair comment, although I'm still puzzled as to how nobody can explain why
this fails
In
for your patience,
Cheers!
--
View this message in context:
http://old.nabble.com/nodosfilewarning-not-working-tp29948673p29948971.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com
/nodosfilewarning-not-working-tp29948673p29949009.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http
On 10/12/2010 10:10 PM, Autotoonz wrote:
defaria wrote:
Being as Chris is the project manager for Cygwin (and an all around nice
and competent guy) I can pretty much guarantee you that yes he did test
it. Wait... He just posted and yes he did do it. This leads me to ask -
did you try it?
Greetings, Autotoonz!
Tim Daneliuk wrote:
You can also permanently set this environment variable from Windows itself
so
that all instantiations of cygwin environments - regardless of shell will
see it.
No I can't, as stated in the OP.
No, you DIDN'T. It's rather clear from your posts,
On Wed, Oct 13, 2010 at 06:31:22AM +0400, Andrey Repin wrote:
Which (this your reply) convincing me even further that you don't have a clue
in how environment variables works.
Come on, there's no need to go so negative here.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ:
On Tue, Oct 12, 2010 at 06:59:26PM -0700, Autotoonz wrote:
I just tried running the batch file directly (as a per the commands
listed above), and the warning is now suppressed. Because I was
calling it from another batch file, the env variable was of course
lost. So my mistake here, although
on this forum then I guess that I would have isolated what caused
this instead of assuming that there was a bug.
Thanks for your help Chris,
cheers.
--
View this message in context:
http://old.nabble.com/nodosfilewarning-not-working-tp29948673p29949816.html
Sent from the Cygwin list mailing
Greetings, prakash babu!
I tried setting it in the under the System Variables section but still I am
getting this warning.
Then,
1. You didn't rebooted your system after setting the variable.
2. The host application clearing the environment before calling your
application.
Is there any
On Thu, Jun 10, 2010 at 12:55, prakash babu wrote:
I have a web application which runs as SYSTEM user in windows.
It executes the following command using Java Runtime.exec api's
C:/cygwin/bin/sh.exe -c C:/cygwin/bin/mkdir.exe -p 'C:/cygwin/tmpdir'
(snip)
Is there any other way to set the
I have a web application which runs as SYSTEM user in windows.
It executes the following command using Java Runtime.exec api's
C:/cygwin/bin/sh.exe -c C:/cygwin/bin/mkdir.exe -p 'C:/cygwin/tmpdir'
The command executes fine but I get the following warning.
cygwin warning:
MS-DOS style path
On 06/10/2010 05:55 AM, prakash babu wrote:
I have a web application which runs as SYSTEM user in windows.
It executes the following command using Java Runtime.exec api's
C:/cygwin/bin/sh.exe -c C:/cygwin/bin/mkdir.exe -p 'C:/cygwin/tmpdir'
The command executes fine but I get the following
=nodosfilewarning not working.
To: cygwin@cygwin.com, jprakashb...@yahoo.co.in
Date: Thursday, June 10, 2010, 5:30 PM
On 06/10/2010 05:55 AM, prakash babu
wrote:
I have a web application which runs as SYSTEM user in
windows.
It executes the following command using Java
Runtime.exec api's
C
On 10 June 2010 12:55, prakash babu wrote:
I have a web application which runs as SYSTEM user in windows.
It executes the following command using Java Runtime.exec api's
C:/cygwin/bin/sh.exe -c C:/cygwin/bin/mkdir.exe -p 'C:/cygwin/tmpdir'
The command executes fine but I get the following
CYGWIN=nodosfilewarning not working.
To: cygwin@cygwin.com
Date: Thursday, June 10, 2010, 7:04 PM
On 10 June 2010 12:55, prakash babu
wrote:
I have a web application which runs as SYSTEM user in
windows.
It executes the following command using Java
Runtime.exec api's
C:/cygwin/bin/sh.exe
On 6/10/2010 11:57 AM, prakash babu wrote:
I tried setting it in the under the System Variables section but still I am
getting this warning.
Is there any other way to set the CYGWIN env variable.
It's unclear if you're running this as a service or not. If you are,
you need to restart the
26 matches
Mail list logo
