Re: control-C to "jumpstart" windows process

It sounds like the quick-edit mode might be the culprit, so I won't comment on that. However, I notice no one has questioned your use of the windows command window.

That's what I'm doing - you're a self-stated unix guy - Why are you using the DOS box?

Please let me wholeheartedly recommend installing cygwin. It's free, and much more importantly it comes with bash (or ash or zsh or csh or even pdksh) and most importantly, much more friendly to 'eunuchs' than windows CMD.exe . (And to my knowledge, there's no funny-business going on with errant mouse clicks in the window.)

--chargrill

s**lil*;  $*=join'',sort split q**;  s;.*;grr; &&s+(.(.)).+$2$1+; $; =
qq-$_-;s,.*,ahc,;$,.=chop for split q,,,reverse;print for($,,$;,$*,$/)
[download]

Comment on Re: control-C to "jumpstart" windows process Download Code

Replies are listed 'Best First'.
Re^2: control-C to "jumpstart" windows process (bashing) by tye (Sage) on Oct 18, 2006 at 20:23 UTC
I have cygwin and use it a lot. I don't use bash (too many things it just doesn't do well under Win32). But I brought up the "bash" prompt since you didn't appear to actually know anything, just make claims about what you don't know. (: The "bash prompt" has exactly the same behavior with regard to mark/select mode and pausing output. You can even turn on "QuickEdit" mode for it. - tye	[reply]
Re^3: control-C to "jumpstart" windows process (bashing) by chargrill (Parson) on Oct 18, 2006 at 22:13 UTC
Sorry, I tend to forget my experiences while working on Windows rather quickly - and, it's been a few months... My usual mode of working within cygwin was to immediately start up X with an xterm, which definitely doesn't have a quick-edit mode and therefore doesn't display that behavior. Having left that out of my earlier statement makes it misleading, so apologies. --chargrill `s*lil; $=join'',sort split q; s;.;grr; &&s+(.(.)).+$2$1+; $; = qq-$_-;s,.,ahc,;$,.=chop for split q,,,reverse;print for($,,$;,$,$/)` [download]	[reply] [d/l]