Re: Sending ctrl-c to running process

On Tue, 09 Sep 2008 12:00:52 -0500
Adam Krolnik <adam.krolnik@xxxxxxxxxxxxxxx> wrote:

> Tried task.abort  - looks good. Needs an indication of the job being 
> killed in the output window.
> 
> I didn't see a way to configure this into the menu that comes up with 3 
> on the output pane. This would be
> a good place to put it.

Context menus other than the main one for filelists are not user-configurable. 
You can, however, create custom menus and pop them up using some part of the UI 
that _is_ configurable.

I never bothered formalising a UI for this action, as it's not considered part 
of the default kit. For testing purposes, I added a button to the commandbar, 
with gtk's 'stop' icon, and assigned the button's action to task.abort.

 Maybe also a config option to either send INT, 
> TERM or KILL signals.

BTW, it's not just for commands, it kills internal actions as well (hence 
'task'). And it's brutish, no clean exits. Don't use it unless you have to.

Regards
Tom

> tpgww@xxxxxxxxxxx wrote:
> > On Mon, 08 Sep 2008 17:23:07 -0500
> > Adam Krolnik <adam.krolnik@xxxxxxxxxxxxxxx> wrote:
> >
> >   
> >> How can I send a control-c to a command started in the command window.
> >> I tried selecting the process and typing <Ctrl-C> but nothing went in.
> >>     
> >
> > Can't. An entered command of the form 'pid:message' (or '0:message' for the 
> > last-started command) will pipe 'message' to that process, but that's not 
> > going to work for <Ctrl>C etc.
> >
> > Need to kill it instead. Select a process from children menu to paste the 
> > relevant pid.
> > Or be brave and enable the largely untested 'task.abort' action and make a 
> > menu-button for that.
> >
> > Regards
> > Tom
> >
> >
> >   
> 
> -- 
>     Soli Deo Gloria
>     Adam Krolnik
>     Director of Design Verification
>     VeriSilicon Inc.
>     Plano TX. 75074
>     Co-author "Assertion-Based Design", "Creating Assertion-Based IP"
> 


-- 
Users can unsubscribe from the list by sending email to 
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by 
logging into the web interface.

Other related posts: