Hi. Andrea Bolognani <[EMAIL PROTECTED]> (02/08/2007): > What I can see, as a user, is that, if I run xterm (or rxvt, or > gnome-terminal, they behave the same) from a terminal window, the > shell is blocked because the new terminal process is in the > foreground, and the shell waits for it to complete before giving me > back the prompt.
If I do the following from an xfce4-terminal window: | xfce4-terminal Or: | xfce4-terminal -x vim /foo/bar Or: | xfce4-terminal.wrapper -e vim /foo/bar Everything is alright: a new terminal window appears, the calling one is blocked, and waiting for the second to terminate. In the 2nd and the 3rd case, vim is spawned correctly. If I use: | xfce4-terminal -e vim /foo/bar (/foo/bar being there or not), I get the following: | LANG=C xfce4-terminal -e vim /tmp 1>/dev/null | Unknown option "/tmp" but you said you were using `xfce4-terminal.wrapper', right? > If I do the same with xfce4-terminal, I immediately get the prompt > back: this is because (my guess of course) xfce4-terminal forks on > startup, or does a similar trick to run in the background; this causes > the shell (or Sylpheed) to think the process terminated, and returns > to do its stuff. What if you `strace' it? (`-f' might help). > It is also different from the expected behavior, since xterm, rxvt and > gnome-terminal all stay in the foreground, and xterm is AFAICT the > reference implementation for terminals. Not different here... Cheers, -- Cyril Brulebois
pgpeqJRl5Fjsg.pgp
Description: PGP signature
