Re: vte_terminal_fork_command behavior

[Ignacio Butler <ibutler gmail com>]

It's true, that can cause my some troubles. I'll avoid overload enviroment.

Thank you

On Sun, Jan 25, 2009 at 9:34 AM, Wouter Bolsterlee <wbolster gnome org> wrote:
> 2009-01-25 klockan 18:29 skrev Ignacio Butler:
>> > Another approach would be to execute  a command like this in the VTE widget:
>> >  sh -c "'YOUR COMMAND LINE GOES HERE'; read;"
>> > In this case the spawned shell will wait for the user to hit Enter (or
>> > Ctrl-C or Ctrl-D) to exit.
>> it worked.
>> Thanks
>
> Hi Ignacio,
>
> I'm glad you got things to work.
>
>> Here is the code:
>> [snip]
>>       char *params[] = {"/bin/sh", "-c", "ls -l ~/;read",NULL};
>
> Make sure that you properly escape any strings you include here, in case you
> do not hardcode it...
>
>>       char *env[] = {"PATH=/usr/bin:/bin:./usr/local/bin:/bin", NULL};
>
> I'm not quite sure this is a good thing to do. Not inheriting the standard
> environment may cause serious issues, like not being able to find programs
> in custom paths, not being able to use the X display, or not being able to
> use the DBus session bus, among many other things.
>
>    — Wouter
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: This message was signed/encrypted using GnuPG.
>
> iD8DBQFJfKKpP7QTTiUKY+sRApCdAJ9T8KH1tSo0vS/g8qdIzphp+b3OTwCfVvQ1
> 04E8Fooqe5zP1AFfVUwgWHg=
> =YAxb
> -----END PGP SIGNATURE-----
>
>



-- 
   -o)
   / \\
_\_V
cuando no tenes paredes, no necesitas ventanas

who | grep -i blonde | talk;
cd ~; wine; talk; touch;
unzip; touch; strip; gasp;
finger; gasp; mount; fsck;
more; yes; gasp; umount;
make clean; sleep;