I had the same problem last week, and I suspect that I somehow mistyped the
DOS variable name
set CYGWIN=nodosfilewarning
When I tried typing it at the DOS command prompt, it worked fine. By that
stage I had overwritten my batch file and removed the nodosfilewarning
variable because I concluded
Andrey Repin-3 wrote:
>
> You should be able to modify USER variables. Even if both System control
> panel
> applet and regedit.exe are blocked, there's tons of ways to deal with
> registry
> directly, down to writing your own little program in any language you
> familiar
> with (almost any com
Lee D. Rothstein wrote:
>
> DOS 'setx' in batch file "A" will affect all subsequently invoked batch
> files from outside "A".
> Is this what you did?
>
No. I used the DOS set command, as discussed. This probably failed due to a
typo on my part, but I'm uncertain.
> 'setx' can also be inv
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 subsequent processes unless the
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? Exactly that, what Chris posted? An
Christopher Faylor-8 wrote:
>
> You haven't provided the exact steps to show what doesn't work. This:
>
>>>On Tue, Oct 12, 2010 at 05:49:31PM -0700, Autotoonz wrote:
>>>>Here is the command line I'm running: C:\cygwin\bin\bash --login
>>
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.
Also, this is no use for surpressing the warning when running individ
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
> Something like this works fine:
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:
http://cygwin.com/cygwin-ug-net/using.html#using-pathnames
A
9 matches
Mail list logo
