comment on

Hey! it works!

The third option you suggested does the job, using as well sh or bash as xterm or gnome-terminal. I include the code:

...
$tks->signal_connect( 'clicked' => sub {
    my $command = "tw pro:$currproj";
    my $ret = fork();
    if($ret == 0) {
        # this is the fork: become $command and go away.
        exec("gnome-terminal", "-e", "bash -c '$command; bash'");
    }
    else { # this is the parent: do nothing and go ahead. }
    return FALSE;
} );
[download]

I detect zombie processes remaining in my ps -e:

 2504 ?        00:00:01 perl
 2509 ?        00:00:01 gnome-terminal <defunct>
 2573 ?        00:00:01 gnome-terminal <defunct>
 2638 ?        00:00:01 gnome-terminal <defunct>
 2702 ?        00:00:01 gnome-terminal <defunct>
 2767 ?        00:00:00 gnome-terminal
 2773 ?        00:00:00 gnome-pty-helpe
[download]

that dissapear when the perl script comes to en end. Thank you very much, Anonymous Wisdom.

In reply to Re^2: Forking an operative terminal by perlgrim
in thread Forking an operative terminal by perlgrim

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.


Keep It Simple, Stupid
	PerlMonks