I'm running 4NT (current version) on a Windows XP system. Recently I
got a spyware program on my machine which messed some things up. I
removed the spyware, but I find that I cannot run any Cygwin utilities
from the 4NT prompt anymore. When I run a program (such as cat, strace,
gcc, make, et
CyberZombie <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
> OT: Any reason why you haven't moved to the Cygwin bash shell? IMO,
> it's much better than 4NT (my prior command-line-of-choice prior to
> Cygwin)...
>
No, I find 4NT to be more flexible than BASH... filename completion is
CyberZombie <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
>>No, I find 4NT to be more flexible than BASH... filename completion is
>>handier, especially when multiple filenames match what you type;
>>editing of environment variables (especially PATH) with eset is
>>unmatched by Bash, and t
t says:
4NT 5.00U Windows XP 5.1
4NT Build 125 Windows XP Build 2600 Service Pack 1
Registered to Daniel Miller
S/N CD600342
Looks like I'm running Windows XP, doesn't it?? That's what *I*
thought...
- But, when I run cygdrive -s, it says:
Cygwin Configuration Diagnostics
C
Christopher Faylor <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
> On Wed, Aug 04, 2004 at 04:29:41AM +0000, Daniel Miller wrote:
>>- If I run "ver /r" from the 4NT window, with my current directory on
>>c: \ (which is my WinXP boot drive), it says:
>>
Christopher Faylor <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
>>gateway to this list.
>
> I found this in your cygcheck output as one of your environment
> variables in the failing 4NT case:
>
> __COMPAT_LAYER = `Win98 DisableThemes '
>
> This is the cause of your problems. I don't
On linux systems, I typically to global searches with a command such as:
find . -name "*.[ch]*" -exec grep -H -n stuff {} \;
and this works nicely. However, when I try the same command under Cygwin
(from a 4NT prompt, not Bash), I get "find: missing argument to '-exec' ".
I tried a vari
I've been using WinXP Pro for awhile now, with few problems. Now, however,
I'm using WinXP Home on one of our systems, and I keep finding things that
work differently on it, which is *very* annoying...
The most recent problem is running one of my Windows console utilities
under Bash. Under WX
"Dave Korn" <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
>> -Original Message-
>> From: cygwin-owner On Behalf Of Daniel Miller
>> Sent: 12 October 2004 19:06
>
>> Does anyone have any idea what XPHome is doing in the Bash
>>
"Dave Korn" <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
>> -Original Message-
>> From: cygwin-owner On Behalf Of Daniel Miller
>> Sent: 12 October 2004 19:06
>
>> under Bash. Under WXPPro/Bash it worked fine. However, under Home
&
Daniel Miller <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
I propose that this is *not* really off-topic, since the problems that I'm
experiencing do not occur in cmd.exe, nor in 4NT, only in Bash. So it's
something Bash is doing in its environment that is breaking S
Daniel Miller <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
> Daniel Miller <[EMAIL PROTECTED]> wrote in
> news:[EMAIL PROTECTED]:
>
> I propose that this is *not* really off-topic, since the problems that
> I'm experiencing do not occur in cmd.exe, nor
Christopher Faylor <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
>>> Daniel Miller <[EMAIL PROTECTED]> wrote in
>>> news:[EMAIL PROTECTED]:
>>>
>>> I propose that this is *not* really off-topic, since the problems
that
>>> I&#x
> On Tue, 12 Oct 2004, Daniel Miller wrote:
>
> > On linux systems, I typically to global searches with a command such as:
> >
> > find . -name "*.[ch]*" -exec grep -H -n stuff {} \;
> >
> > and this works nicely. However, when I try the same co
14 matches
Mail list logo
