Re: cmd.exe from Cygwin

Jeenu V wrote: On Thu, Jan 8, 2009 at 9:36 PM, Christopher Faylor wrote: . It's not good to feed the spammers. Thanks. Do you think screen is the only thing that uses ptys in the whole distribu

Re: cmd.exe from Cygwin

On Thu, Jan 8, 2009 at 9:36 PM, Christopher Faylor wrote: > Do you think screen is the only thing that uses ptys in the whole > distribution? Nope; I've no idea. -- :J -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Doc

Re: cmd.exe from Cygwin

On Thu, Jan 08, 2009 at 04:03:03PM +0530, Jeenu V wrote: >On Thu, Jan 8, 2009 at 6:32 AM, Jeenu V wrote: >> On Wed, Jan 7, 2009 at 9:22 PM, Christopher Faylor >> wrote: >> >>> screen uses ptys. ptys are equivalent to CYGWIN=tty. >>> >>> We really don't guarantee that pure Windows applications wi

Re: cmd.exe from Cygwin

On Thu, Jan 8, 2009 at 4:50 PM, Corinna Vinschen wrote: > It's a constraint of the native Windows applications. There's no > PTY concept in Windows so Cygwin uses pipes to emulate the behaviour. > Cygwin applications know when they are running in a pty, native apps > don't and behave differently

Re: cmd.exe from Cygwin

On Jan 8 16:03, Jeenu V wrote: > On Thu, Jan 8, 2009 at 6:32 AM, Jeenu V wrote: > > On Wed, Jan 7, 2009 at 9:22 PM, Christopher Faylor > > wrote: > > > >> screen uses ptys. ptys are equivalent to CYGWIN=tty. > >> > >> We really don't guarantee that pure Windows applications will work with > >>

Re: cmd.exe from Cygwin

On Thu, Jan 8, 2009 at 6:32 AM, Jeenu V wrote: > On Wed, Jan 7, 2009 at 9:22 PM, Christopher Faylor > wrote: > >> screen uses ptys. ptys are equivalent to CYGWIN=tty. >> >> We really don't guarantee that pure Windows applications will work with >> ptys. > > Hm... looks like I've to live without

Re: cmd.exe from Cygwin

On Wed, Jan 7, 2009 at 9:22 PM, Christopher Faylor wrote: > screen uses ptys. ptys are equivalent to CYGWIN=tty. > > We really don't guarantee that pure Windows applications will work with > ptys. Hm... looks like I've to live without cmd.exe from screen. Anyway,.thank you guys for the support

Re: cmd.exe from Cygwin

On Wed, Jan 07, 2009 at 01:49:46PM +0530, Jeenu V wrote: >On Wed, Jan 7, 2009 at 11:41 AM, Larry Hall (Cygwin) > wrote: >> Jeenu V wrote: > >> With cgf's help and a good look at your cygcheck output, I believe I was >> able to reproduce something like your problem. If I'm right, then you >> want t

Re: cmd.exe from Cygwin

On Wed, Jan 7, 2009 at 11:41 AM, Larry Hall (Cygwin) wrote: > Jeenu V wrote: > With cgf's help and a good look at your cygcheck output, I believe I was > able to reproduce something like your problem. If I'm right, then you > want to remove 'tty' from your CYGWIN environment variable. Make sure

Re: cmd.exe from Cygwin

Jeenu V wrote: On Tue, Jan 6, 2009 at 11:23 PM, Larry Hall (Cygwin) wrote: Larry Hall (Cygwin) wrote: I know you've looked at the environment differences on your machine between a plain cmd and one under bash. How about comparing yours under bash with your colleague's? Also, does the shell

Re: cmd.exe from Cygwin

On Tue, Jan 6, 2009 at 11:23 PM, Larry Hall (Cygwin) wrote: > Larry Hall (Cygwin) wrote: >> I know you've looked at the environment differences on your machine >> between a plain cmd and one under bash. How about comparing yours >> under bash with your colleague's? Also, does the shell matter?

Re: cmd.exe from Cygwin

Larry Hall (Cygwin) wrote: Jeenu V wrote: On Tue, Jan 6, 2009 at 10:43 AM, Jeenu V wrote: [...] I checked with one of my colleagues who has Cygwin installed, but he doesn't seem to have this problem. I feel like going with a fresh installation. I did a fresh, quick and bare-minimum installati

Re: cmd.exe from Cygwin

Jeenu V wrote: On Tue, Jan 6, 2009 at 10:43 AM, Jeenu V wrote: [...] I checked with one of my colleagues who has Cygwin installed, but he doesn't seem to have this problem. I feel like going with a fresh installation. I did a fresh, quick and bare-minimum installation (to a different directory

Re: cmd.exe from Cygwin

On Tue, Jan 6, 2009 at 10:43 AM, Jeenu V wrote: [...] > I checked with one of my colleagues who has Cygwin installed, but he > doesn't seem to have this problem. I feel like going with a fresh > installation. I did a fresh, quick and bare-minimum installation (to a different directory, but keepin

Re: cmd.exe from Cygwin

Jeenu V wrote: On Tue, Jan 6, 2009 at 10:51 AM, Larry Hall (Cygwin) wrote: OK, sounds like an environment problem then. You could probably spot the issue by comparing the environment you get in bash with the one you get in cmd.exe. I did that already and that was how I came to know I could s

Re: cmd.exe from Cygwin

On Tue, Jan 6, 2009 at 10:51 AM, Larry Hall (Cygwin) wrote: > OK, sounds like an environment problem then. You could probably spot > the issue by comparing the environment you get in bash with the one > you get in cmd.exe. I did that already and that was how I came to know I could solve the orig

Re: cmd.exe from Cygwin

Jeenu V wrote: On Tue, Jan 6, 2009 at 10:00 AM, Larry Hall (Cygwin) wrote: And I assume that you don't have this problem if you just invoke 'cmd.exe' from Windows and try the same thing and further that it does reproduce if you then invoke 'bash' from that command prompt and then 'cmd.exe' agai

Re: cmd.exe from Cygwin

On Tue, Jan 6, 2009 at 10:00 AM, Larry Hall (Cygwin) wrote: > And I assume that you don't have this problem if you just invoke > 'cmd.exe' from Windows and try the same thing and further that it > does reproduce if you then invoke 'bash' from that command prompt > and then 'cmd.exe' again. cmd.ex

Re: cmd.exe from Cygwin

Jeenu V wrote: On Tue, Jan 6, 2009 at 9:37 AM, Larry Hall (Cygwin) wrote: ^^ . Thanks. I can't reproduce this. Do you have that problem before you invoke 'cmd'? Sad :(. I don't have any problems before in

Re: cmd.exe from Cygwin

On Tue, Jan 6, 2009 at 9:37 AM, Larry Hall (Cygwin) wrote: > I can't reproduce this. Do you have that problem before you invoke > 'cmd'? Sad :(. I don't have any problems before invoking cmd.exe; bash just works fine. Would you suggest a fresh install of Cygwin? I hope you watched the screencast

Re: cmd.exe from Cygwin

Jeenu V wrote: On Tue, Jan 6, 2009 at 8:36 AM, Larry Hall (Cygwin) wrote: You mean the part about the text overwrtiting itself? Your 'TERM' environment variable is set to 'screen'. Make sure that it's set to 'cygwin' and you'll see less trouble. ;-) Ehm... that was because I was using screen

Re: cmd.exe from Cygwin

On Tue, Jan 6, 2009 at 8:36 AM, Larry Hall (Cygwin) wrote: > You mean the part about the text overwrtiting itself? Your 'TERM' > environment variable is set to 'screen'. Make sure that it's set > to 'cygwin' and you'll see less trouble. ;-) Ehm... that was because I was using screen when I gene

Re: cmd.exe from Cygwin

On 01/05/2009, Jeenu V wrote: > I did not have a chance to, no. Is there something there that you believe > > significantly changes the context of your original question? Well, I initially thought these two problems were related. But now that one appear to be solved, and and other remains, I th

Re: cmd.exe from Cygwin

> Maybe the best thing to do would be to edit the .bat/.cmd file so that the > first thing it does is redefines PATH as it is in a normal cmd window - ie > w/o cygwin running. > That would result in the environment being clean for cygwin normally, and > mean your symbian stuff wouldn't end up crapp

Re: cmd.exe from Cygwin

Larry Hall (Cygwin) wrote: Jeenu V wrote: On Mon, Jan 5, 2009 at 9:53 PM, Larry Hall (Cygwin) wrote: The Cygwin paths are added in '/etc/profile'. Obviously, you can remove them though that will make your configuration non-standard and unsupported. Essentially, this would make Cygwin tools

Re: cmd.exe from Cygwin

Jeenu V wrote: On Mon, Jan 5, 2009 at 9:53 PM, Larry Hall (Cygwin) wrote: The Cygwin paths are added in '/etc/profile'. Obviously, you can remove them though that will make your configuration non-standard and unsupported. Essentially, this would make Cygwin tools inaccessible when running 'b

Re: cmd.exe from Cygwin

On Mon, Jan 5, 2009 at 9:53 PM, Larry Hall (Cygwin) wrote: > The Cygwin paths are added in '/etc/profile'. Obviously, you can > remove them though that will make your configuration non-standard > and unsupported. Essentially, this would make Cygwin tools > inaccessible when running 'bash', whic

Re: cmd.exe from Cygwin

Jeenu V wrote: For all we know bldmake could be bldmake.bat which contains a line such as: sh E:\Symbian\M04765_Symbain_OS_V9.5\bin\Tech\Viewepoc32\tools\bldmake.bat Intending to use Symbian's version of "sh" which can handle backslashes but due to how your PATH is setup it's using Cygwin's ver

Re: cmd.exe from Cygwin

> For all we know bldmake could be bldmake.bat which contains a line such as: > > sh E:\Symbian\M04765_Symbain_OS_V9.5\bin\Tech\Viewepoc32\tools\bldmake.bat > > Intending to use Symbian's version of "sh" which can handle backslashes but > due to how your PATH is setup it's using Cygwin's version of

Re: cmd.exe from Cygwin

Jeenu V wrote: N:\src\CEDAR\GENERIC\base\bsp\hwip_arm\rvemuboard\ct1136\test>cmd /c bldmake bldfiles ARMV6 sh: E:SymbianM04765_Symbian_OS_v9.5binTechViewepoc32toolsbldmake.bat: command not found If you see above example, all I run is a command 'bldmake' which neither contain back-slash nor white

Re: cmd.exe from Cygwin

Jeenu V wrote: > The program I intend to run with cmd.exe (with /c switch) fails to run > as it couldn't access some Windows paths. Please take a look like this > command, for example: > > N:\src\CEDAR\GENERIC\base\bsp\hwip_arm\rvemuboard\ct1136\test>cmd /c > bldmake bldfiles ARMV6 > sh: E:Symbian

Re: cmd.exe from Cygwin

Thanks for the reply. > > The backslash is an escape character, so you need to get it treated as > a character somehow - escaping ("\\") or inside quotes works for me: > I'm aware of this. >> N:\src\CEDAR\GENERIC\base\bsp\hwip_arm\rvemuboard\ct1136\test>cmd /c >> bldmake bldfiles ARMV6 >> sh: E:

Re: cmd.exe from Cygwin

On 1/2/09, Jeenu V wrote: > Hi, > > I've to run some windows commands repeatedly. Since I'm familiar and > comfortable with BASH, I thought I would perform the 'intelligent' > decisions using BASH scripts and run rest using cmd.exe invoked from > Cygwin bash shell. But this is the problem I face: