Re: cmd.exe from Cygwin
On Thu, Jan 8, 2009 at 6:32 AM, Jeenu V jee...@gmail.com wrote: On Wed, Jan 7, 2009 at 9:22 PM, Christopher Faylor cgf-use-the-mailinglist-ple...@cygwin.com 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 and help. And can this be guaranteed in future versions of Cygwin? Or is it something constrained by screen? -- :J -- 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: cmd.exe from Cygwin
On Jan 8 16:03, Jeenu V wrote: On Thu, Jan 8, 2009 at 6:32 AM, Jeenu V jee...@gmail.com wrote: On Wed, Jan 7, 2009 at 9:22 PM, Christopher Faylor cgf-use-the-mailinglist-ple...@cygwin.com 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 and help. And can this be guaranteed in future versions of Cygwin? Or is it something constrained by screen? 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 if their stdio descriptors are connected to pipes. Bottom line: We just *can't* gurantee ... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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: cmd.exe from Cygwin
On Thu, Jan 8, 2009 at 4:50 PM, Corinna Vinschen corinna-cyg...@cygwin.com 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 if their stdio descriptors are connected to pipes. Bottom line: We just *can't* gurantee ... OK. I understand. Thanks. -- :J -- 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: 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 jee...@gmail.com wrote: On Wed, Jan 7, 2009 at 9:22 PM, Christopher Faylor cgf-use-the-mailinglist-ple...@cygwin.com 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 and help. And can this be guaranteed in future versions of Cygwin? Or is it something constrained by screen? Do you think screen is the only thing that uses ptys in the whole distribution? 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: cmd.exe from Cygwin
On Thu, Jan 8, 2009 at 9:36 PM, Christopher Faylor cgf-use-the-mailinglist-ple...@cygwin.com 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 Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: cmd.exe from Cygwin
Jeenu V wrote: On Thu, Jan 8, 2009 at 9:36 PM, Christopher Faylor cgf-use-the-mailinglist-please AT cygwin DOT com wrote: http://cygwin.com/acronyms/#PCYMTNQREAIYR. It's not good to feed the spammers. Thanks. Do you think screen is the only thing that uses ptys in the whole distribution? Nope; I've no idea. ptys are a commonly used facility under Linux/Unix and so also on Cygwin. 'screen' is not the only Cygwin package that makes use of them. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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: cmd.exe from Cygwin
On Wed, Jan 7, 2009 at 11:41 AM, Larry Hall (Cygwin) reply-to-list-only...@cygwin.com 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 you exit *all* Cygwin processes, including services, before firing up bash again and invoking 'cnd' from there to test. Oh yeah! That works. Thank you. But here the catch: it behaves the same old way if I invoke cmd.exe from screen. Setting $TERM as cygwin doesn't seem to work either. Interestingly my colleague too has this problem with screen. :( -- :J -- 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: 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) reply-to-list-only...@cygwin.com 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 you exit *all* Cygwin processes, including services, before firing up bash again and invoking 'cnd' from there to test. Oh yeah! That works. Thank you. But here the catch: it behaves the same old way if I invoke cmd.exe from screen. Setting $TERM as cygwin doesn't seem to work either. Interestingly my colleague too has this problem with screen. :( screen uses ptys. ptys are equivalent to CYGWIN=tty. We really don't guarantee that pure Windows applications will work with ptys. 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: cmd.exe from Cygwin
On Wed, Jan 7, 2009 at 9:22 PM, Christopher Faylor cgf-use-the-mailinglist-ple...@cygwin.com 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 and help. -- :J -- 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: cmd.exe from Cygwin
On Tue, Jan 6, 2009 at 10:43 AM, Jeenu V jee...@gmail.com 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 keeping the old one intact), but the problem still seem to exist. Do you think this is a bug? If so what if I want to report this as one - where would I do that, in this list or dev? -- :J -- 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: 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, but keeping the old one intact), but the problem still seem to exist. Do you think this is a bug? If so what if I want to report this as one - where would I do that, in this list or dev? Bugs are reported to this list. 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? Does it happen for you with tcsh, pdksh, or zsh too? This might provide some insight. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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: 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 installation (to a different directory, but keeping the old one intact), but the problem still seem to exist. Do you think this is a bug? If so what if I want to report this as one - where would I do that, in this list or dev? Bugs are reported to this list. 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? Does it happen for you with tcsh, pdksh, or zsh too? This might provide some insight. Almost forgot. One more thing and probably the most important. Is this reproducible with the upcoming Cygwin 1.7 release? http://cygwin.com/ml/cygwin-announce/2008-12/msg9.html -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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: cmd.exe from Cygwin
On Tue, Jan 6, 2009 at 11:23 PM, Larry Hall (Cygwin) reply-to-list-only...@cygwin.com 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? Does it happen for you with tcsh, pdksh, or zsh too? This might provide some insight. Almost forgot. One more thing and probably the most important. Is this reproducible with the upcoming Cygwin 1.7 release? I installed 1.7 I tried with other shells you mentioned I sourced my colleagues enviornement variables to my bash None made a difference! :(. I started suspecting my PC more, though I'm not sure how to pin the problem down. Any clues? -- :J -- 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: cmd.exe from Cygwin
Jeenu V wrote: On Tue, Jan 6, 2009 at 11:23 PM, Larry Hall (Cygwin) reply-to-list-only...@cygwin.com 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? Does it happen for you with tcsh, pdksh, or zsh too? This might provide some insight. Almost forgot. One more thing and probably the most important. Is this reproducible with the upcoming Cygwin 1.7 release? I installed 1.7 I tried with other shells you mentioned I sourced my colleagues enviornement variables to my bash None made a difference! :(. I started suspecting my PC more, though I'm not sure how to pin the problem down. Any clues? 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 you exit *all* Cygwin processes, including services, before firing up bash again and invoking 'cnd' from there to test. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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: 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 version of sh which doesn't like the backslashes. I'm not saying that's exactly what's going on, I'm saying that we don't know given your description so far. I think I've make little progress in this regard: I compared environment variables from an original cmd.exe and that of cmd.exe invoked from cygwin bash. I noticed that, for the one invoked from cygwin, the %Path% variable had cygwin\bin directories before all Windows paths. After I removed the cygwin\bin directories, the same utility seem to work fine (as of now). How can I prevent cygwin\bin directories occupying at the beginning of %path%? 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', which doesn't sound like what you really want. Obviously, you could add the Cygwin paths somewhere else to give Symbian priority but this is likely to just cause other conflicts and, again, not be what you really want. So to me, the question comes down to which tools to you really want to use, Symbian's, Cygwin's, or something else? Once you can answer that, you should be able to configure things so that you get the proper set for your needs. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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: cmd.exe from Cygwin
On Mon, Jan 5, 2009 at 9:53 PM, Larry Hall (Cygwin) reply-to-list-only...@cygwin.com 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', which doesn't sound like what you really want. Obviously, you could add the Cygwin paths somewhere else to give Symbian priority but this is likely to just cause other conflicts and, again, not be what you really want. So to me, the question comes down to which tools to you really want to use, Symbian's, Cygwin's, or something else? Once you can answer that, you should be able to configure things so that you get the proper set for your needs. Thanks for the info. My intention is not to throw Cygwin and it's utilities away; but to move Cygwin path towards the end when--and only when--I run Symbian tool chain, because, AFAIK, Symbian tool chain doesn't ask for any tools from Cygwin. By the way, did anybody get a change to look at my screencast? -- :J -- 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: cmd.exe from Cygwin
Jeenu V wrote: On Mon, Jan 5, 2009 at 9:53 PM, Larry Hall (Cygwin) reply-to-list-only...@cygwin.com 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', which doesn't sound like what you really want. Obviously, you could add the Cygwin paths somewhere else to give Symbian priority but this is likely to just cause other conflicts and, again, not be what you really want. So to me, the question comes down to which tools to you really want to use, Symbian's, Cygwin's, or something else? Once you can answer that, you should be able to configure things so that you get the proper set for your needs. Thanks for the info. My intention is not to throw Cygwin and it's utilities away; but to move Cygwin path towards the end when--and only when--I run Symbian tool chain, because, AFAIK, Symbian tool chain doesn't ask for any tools from Cygwin. But your batch file is invoking Cygwin's bash. Perhaps if you decouple things there, then they will work as you expect without changing other things in your environment. Moving Cygwin paths to the end of the path in '/etc/profile' would have the effect of making everything else in the system with a like name override the Cygwin version, even when you're using Cygwin and want the Cygwin versions. I expect this is not at all what you want. By the way, did anybody get a change to look at my screencast? I did not have a chance to, no. Is there something there that you believe significantly changes the context of your original question? -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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: 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 sh which doesn't like the backslashes. I'm not saying that's exactly what's going on, I'm saying that we don't know given your description so far. I think I've make little progress in this regard: I compared environment variables from an original cmd.exe and that of cmd.exe invoked from cygwin bash. I noticed that, for the one invoked from cygwin, the %Path% variable had cygwin\bin directories before all Windows paths. After I removed the cygwin\bin directories, the same utility seem to work fine (as of now). How can I prevent cygwin\bin directories occupying at the beginning of %path%? Also, I created a screen cast of running cmd.exe from bash. Please take a look and see if it's a known issue or is something that any of you had previously come across (full-screen view is preferable) http://www.screentoaster.com/watch/stWElTQ0ZKRFhbRVleX1xc -- :J cygcheck.out Description: Binary data -- 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: cmd.exe from Cygwin
Larry Hall (Cygwin) wrote: Jeenu V wrote: On Mon, Jan 5, 2009 at 9:53 PM, Larry Hall (Cygwin) reply-to-list-only...@cygwin.com 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', which doesn't sound like what you really want. Obviously, you could add the Cygwin paths somewhere else to give Symbian priority but this is likely to just cause other conflicts and, again, not be what you really want. So to me, the question comes down to which tools to you really want to use, Symbian's, Cygwin's, or something else? Once you can answer that, you should be able to configure things so that you get the proper set for your needs. Thanks for the info. My intention is not to throw Cygwin and it's utilities away; but to move Cygwin path towards the end when--and only when--I run Symbian tool chain, because, AFAIK, Symbian tool chain doesn't ask for any tools from Cygwin. But your batch file is invoking Cygwin's bash. Perhaps if you decouple things there, then they will work as you expect without changing other things in your environment. Moving Cygwin paths to the end of the path in '/etc/profile' would have the effect of making everything else in the system with a like name override the Cygwin version, even when you're using Cygwin and want the Cygwin versions. I expect this is not at all what you want. 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 crapping itself by calling cygwin tools that work differently.. Chris -- 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: 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 crapping itself by calling cygwin tools that work differently.. Yup, this is what I had in mind. Thanks. 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 think it's worth taking a look. I'll also check with other Cygwin users around me if they face the same problem. Or is it best that I start another thread altogether? -- :J -- 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: 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 think it's worth taking a look. I'll also check with other Cygwin users around me if they face the same problem. Or is it best that I start another thread altogether? 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. ;-) -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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: cmd.exe from Cygwin
On Tue, Jan 6, 2009 at 8:36 AM, Larry Hall (Cygwin) reply-to-list-only...@cygwin.com 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 generated that cygcheck output and when recorded screen cast. I tried invoking cmd.exe from a fresh Cygwin shell (i.e. $TERM is set to 'cygwin'), but the problems still exist. -- :J -- 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: 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 when I generated that cygcheck output and when recorded screen cast. I tried invoking cmd.exe from a fresh Cygwin shell (i.e. $TERM is set to 'cygwin'), but the problems still exist. I can't reproduce this. Do you have that problem before you invoke 'cmd'? -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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: cmd.exe from Cygwin
On Tue, Jan 6, 2009 at 9:37 AM, Larry Hall (Cygwin) reply-to-list-only...@cygwin.com 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 to see what's going on. -- :J -- 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: cmd.exe from Cygwin
Jeenu V wrote: On Tue, Jan 6, 2009 at 9:37 AM, Larry Hall (Cygwin) reply-to-list-only-lh AT cygwin SQUAT com wrote: ^^ http://cygwin.com/acronyms/#PCYMTNQREAIYR. Thanks. 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 to see what's going on. 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. I watched the screencast. That's how I came to understand the problem you were seeing. I wouldn't say I couldn't reproduce it otherwise. I try really hard not to lie about this kind of thing. ;-) -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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: cmd.exe from Cygwin
On Tue, Jan 6, 2009 at 10:00 AM, Larry Hall (Cygwin) reply-to-list-only...@cygwin.com 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.exe from Windows: no; it behaves normally cmd.exe - bash - cmd.exe: same problem I watched the screencast. That's how I came to understand the problem you were seeing. I wouldn't say I couldn't reproduce it otherwise. I try really hard not to lie about this kind of thing. ;-) Just making sure, you know :) 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. -- :J -- 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: cmd.exe from Cygwin
Jeenu V wrote: On Tue, Jan 6, 2009 at 10:00 AM, Larry Hall (Cygwin) reply-to-list-only...@cygwin.com 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.exe from Windows: no; it behaves normally cmd.exe - bash - cmd.exe: same problem 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 watched the screencast. That's how I came to understand the problem you were seeing. I wouldn't say I couldn't reproduce it otherwise. I try really hard not to lie about this kind of thing. ;-) Just making sure, you know :) Yep. 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. Fair enough. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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: cmd.exe from Cygwin
On Tue, Jan 6, 2009 at 10:51 AM, Larry Hall (Cygwin) reply-to-list-only...@cygwin.com 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 original problem by modifying %path%. PATH is the only variable whose contents differed - %path% was prefixed with Cygwin bin directories. Also there were new variables inherited from bash which were: EDITOR=env -u DISPLAY vim FIGNORE=.svn:.o:~ HOME=h:\ HOSTNAME=blr-win-217 INFOPATH=/usr/local/info:/usr/share/info:/usr/info: MAKE_MODE=unix MANPATH=/usr/local/man:/usr/share/man:/usr/man::/usr/ssl/man OLDPWD=/cygdrive/e/Symbian/M04765_Symbian_OS_v9.5/src/CEDAR/GENERIC/base/bsp/hwip_arm/rvemuboard/falcon PRINTER=Microsoft Office Document Image Writer PS1=e[22;31mHe[00m [e[22;32mwe[00m]n! $ PS3= PWD=/cygdrive/h SHLVL=1 SVN_EDITOR=env -u DISPLAY vim +set tw=100 TERM=cygwin USER=jeevis01 _=/cygdrive/c/WINDOWS/system32/cmd But, I don't see anything harmful here. -- :J -- 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: cmd.exe from Cygwin
Jeenu V wrote: On Tue, Jan 6, 2009 at 10:51 AM, Larry Hall (Cygwin) reply-to-list-only...@cygwin.com 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 original problem by modifying %path%. PATH is the only variable whose contents differed - %path% was prefixed with Cygwin bin directories. Also there were new variables inherited from bash which were: snip But, I don't see anything harmful here. Not obviously to cmd.exe anyway... -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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: cmd.exe from Cygwin
Jeenu V wrote: N:\src\CEDAR\GENERIC\base\bsp\hwip_arm\rvemuboard\ct1136\testcmd /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-space. So there's no need to quote the file name here. What 'bldmake' really is--whether .bat, .com or .exe--it's for cmd.exe to find out, of course using %PATH%. In my case, going by the output, it did locate a .bat file with the name 'bldmake'. However, I suspect, something went wrong in the path translation. But the 'sh: ' in the error output rings in my head. Nobody here knows what the contents of bldmake is. As David pointed out a simply execution of cmd /c works fine. So the question is what is bldmake. It seems to be attempting to re-execute itself down some path on the E drive and as David also pointed out, probably trips up on Cygwin in the path somewhere. Take bldmake apart and put some echo statements in there to isolate where the problem really is. Talking about black-slashes: assuming it's a .bat file, as long as the content is interpreted by cmd.exe, the back-slashes inside the script shouldn't make a difference. 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 sh which doesn't like the backslashes. I'm not saying that's exactly what's going on, I'm saying that we don't know given your description so far. -- Andrew DeFaria http://defaria.com He's not dead, he's electroencephalographically challenged. -- 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/
cmd.exe from Cygwin
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: 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\testcmd /c bldmake bldfiles ARMV6 sh: E:SymbianM04765_Symbian_OS_v9.5binTechViewepoc32toolsbldmake.bat: command not found There are two things that I'm surprised about: 1) How come a command launched from cmd.exe spits an error message starting with 'sh:'? 2) Why are back-slashes stripped-off from the path in output message? Also it came to my notice that cmd.exe invoked from a Cygwin bash shell doesn't really behave like the Windows cmd.exe. For example, if you press up-arrow, the cursor goes flying over the window and the display sometimes goes for a toss. Keys like F7 and F8 doesn't work either. It would suffice--as of now, at least--if I could launch a cmd.exe--separate and independent--window from a Cygwin shell. I could try explorer.exe c:\windows\system32\cmd.exe but I'm unable to pass parameters to cmd.exe (say /c or a batch file name). Please help. -- Thanks Jeenu -- 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: cmd.exe from Cygwin
On 1/2/09, Jeenu V jee...@gmail.com 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: 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: The backslash is an escape character, so you need to get it treated as a character somehow - escaping (\\) or inside quotes works for me: $ cmd /c c:\util\showdev.bat 'c:utilshowdev.bat' is not recognized as an internal or external command, operable program or batch file. $ cmd /c c:\\util\\showdev.bat C:\cygwin\home\Leeset devmgr_show_nonpresent_devices=1 C:\cygwin\home\Leecd\windows\system32 C:\Windows\System32start devmgmt.msc $ cmd /c c:\util\showdev.bat C:\cygwin\home\Leeset devmgr_show_nonpresent_devices=1 C:\cygwin\home\Leecd\windows\system32 C:\Windows\System32start devmgmt.msc Regards, Lee N:\src\CEDAR\GENERIC\base\bsp\hwip_arm\rvemuboard\ct1136\testcmd /c bldmake bldfiles ARMV6 sh: E:SymbianM04765_Symbian_OS_v9.5binTechViewepoc32toolsbldmake.bat: command not found There are two things that I'm surprised about: 1) How come a command launched from cmd.exe spits an error message starting with 'sh:'? 2) Why are back-slashes stripped-off from the path in output message? Also it came to my notice that cmd.exe invoked from a Cygwin bash shell doesn't really behave like the Windows cmd.exe. For example, if you press up-arrow, the cursor goes flying over the window and the display sometimes goes for a toss. Keys like F7 and F8 doesn't work either. It would suffice--as of now, at least--if I could launch a cmd.exe--separate and independent--window from a Cygwin shell. I could try explorer.exe c:\windows\system32\cmd.exe but I'm unable to pass parameters to cmd.exe (say /c or a batch file name). Please help. -- Thanks Jeenu -- 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/ -- 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: 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\testcmd /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-space. So there's no need to quote the file name here. What 'bldmake' really is--whether .bat, .com or .exe--it's for cmd.exe to find out, of course using %PATH%. In my case, going by the output, it did locate a .bat file with the name 'bldmake'. However, I suspect, something went wrong in the path translation. But the 'sh: ' in the error output rings in my head. Talking about black-slashes: assuming it's a .bat file, as long as the content is interpreted by cmd.exe, the back-slashes inside the script shouldn't make a difference. It would suffice--as of now, at least--if I could launch a cmd.exe--separate and independent--window from a Cygwin shell. I could try Update: I tried with cygstart.exe, I don't see a difference from starting it with cygstart.exe and the above example. I.e. back-slashes are truncated and output said 'sh: '. -- Thanks Jeenu -- 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: 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\testcmd /c bldmake bldfiles ARMV6 sh: E:SymbianM04765_Symbian_OS_v9.5binTechViewepoc32toolsbldmake.bat: command not found There are two things that I'm surprised about: 1) How come a command launched from cmd.exe spits an error message starting with 'sh:'? 2) Why are back-slashes stripped-off from the path in output message? My WAG: You're using some kind of embedded toolchain for Symbian that is based on the gnu tools, and there's some kind of PATH-clash going on between those and the Cygwin versions. Maybe it shipped with a mingw32-ish sh.exe that it's trying to invoke and your Cygwin sh.exe is getting in there first? We'll need to see your cygcheck output (as described at http://cygwin.com/problems.html, please take special note of the request to send it as an attachment rather than inline body text, TIA) to get an idea if that's happening. Also it came to my notice that cmd.exe invoked from a Cygwin bash shell doesn't really behave like the Windows cmd.exe. For example, if you press up-arrow, the cursor goes flying over the window and the display sometimes goes for a toss. Keys like F7 and F8 doesn't work either. It would suffice--as of now, at least--if I could launch a cmd.exe--separate and independent--window from a Cygwin shell. I could try explorer.exe c:\windows\system32\cmd.exe but I'm unable to pass parameters to cmd.exe (say /c or a batch file name). That's bizarre but could be related. For me, just invoking cmd.exe directly at a Cygwin prompt works fine. ~ $ cmd.exe /c echo foo foo ~ $ If I want a separate shell, cygstart cmd.exe launches it in its own console window. Are you running in a console (DOS) window or a terminal such as rxvt? It'll only work well in a console. cheers, DaveK -- 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/
