comment on

I just wind up hammering ctrl-c till the prompt comes back (sometimes whilst muttering obscenities just slightly too audibly for an open plan office).

But what if you wanted to kill just the child and keep the parent running?

From the perspective of the end user, this distinction doesn't make much sense. If I run a command, and then hit ctrl-c, then I want it to kill the command I ran. I just don't care how that command was implemented: whether it was implemented with a single process or a whole tree of them.

(I might appreciate special handling of ctrl-c if the command I ran provides some sort of interactive environment (eg a command line text editor). That would probably need to be considered on a case-by-case basis.)

Many annoying things. Even the weather is abysmal today. Grr.

This post was brought to you by the adjectives "grumpy" and "wet".

--
.sig : File not found.

In reply to Re^2: system() requires double ctrl-c (cases) by wol
in thread system() requires double ctrl-c by saintmike

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Don't ask to ask, just ask
	PerlMonks