background terminal

2002-06-30 Thread Ciprian Popovici
I did the following: * launch a terminal window * from it, launch another (ie. $ aterm) * the new terminal windows works ok, the old one is waiting for the other to finish in order to resume * in the first window I press ctrl-z and send the second to background * the second window freezes and

Re: background terminal

2002-06-30 Thread Martin Rowe
On Sunday 30 June 2002 10:52 am, Ciprian Popovici wrote: I did the following: * launch a terminal window * from it, launch another (ie. $ aterm) * the new terminal windows works ok, the old one is waiting for the other to finish in order to resume * in the first window I press ctrl-z and

Re: background terminal

2002-06-30 Thread xOr
On Sun, Jun 30, 2002 at 12:52:13PM +0300, Ciprian Popovici wrote: I did the following: * launch a terminal window * from it, launch another (ie. $ aterm) * the new terminal windows works ok, the old one is waiting for the other to finish in order to resume * in the first window I press

Re: background terminal

2002-06-30 Thread Sean 'Shaleh' Perry
On 30-Jun-2002 xOr wrote: On Sun, Jun 30, 2002 at 12:52:13PM +0300, Ciprian Popovici wrote: I did the following: * launch a terminal window * from it, launch another (ie. $ aterm) * the new terminal windows works ok, the old one is waiting for the other to finish in order to resume * in

Re: background terminal

2002-06-30 Thread Kolbe Kegel
it sounds like he's a little confused about what ctrl-z does... he says he uses it to send the process to the background, but that's not what ctrl-z does at all. ctrl-z just *stops* the process. while stopped, it can't do anything. it can't respond to input, create output, or receive events

Re: background terminal

2002-06-30 Thread Martin Rowe
On Sunday 30 June 2002 7:16 pm, Kolbe Kegel wrote: it sounds like he's a little confused about what ctrl-z does... he says he uses it to send the process to the background, but that's not what ctrl-z does at all. ctrl-z just *stops* the process. while stopped, it can't do anything. it can't

Re: execution of commands on startup

2002-06-30 Thread Scott Furt
Sam Halliday wrote: put everything you want into a file, say ~/bin/startbb. Then put exec ~/bin/startbb into your .xinitrc - bam, same thing as exec starkde, exec wmaker, exec gnome-session whaterver. but that achieves nothing... i dont like putting anything into an xinitrc file, i like to

Re: execution of commands on startup

2002-06-30 Thread Scott Furt
Jan Schaumann wrote: Sam Halliday [EMAIL PROTECTED] wrote: How about making a startbb script and then running that from .xinitrc i want to rid the .xinitrc startup usgae in the first place How are you planning on doing this? AFAIK, you gotta have a .xinitrc (unless you make blackbox

Re: execution of commands on startup

2002-06-30 Thread Jan Schaumann
Scott Furt [EMAIL PROTECTED] wrote: Jan Schaumann wrote: AFAIK, you gotta have a .xinitrc (unless you make blackbox your default windowmanager systemwide). Not if you're using a graphical login manager for X. To my knowledge, XDM and KDM (the two that i've used) don't need/use .xinitrc