Re: background terminal

2002-07-01 Thread Ciprian Popovici

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.

Yes, that's what I meant. OK, since there's no problem thanks for clearing
that up.

Ciprian Popovici



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 respond to input, create output, or receive
> events from blackbox or anything else. what you need to do to send the
> process to the background is press ctrl-z and then type "bg", as martin
> illustrated in his example but didn't point out explicitly.

Hi Kolbe

I was assuming my emple was exactly what Ciprian was doing, as he said

> >* in the first window I press ctrl-z and send the second to background

As he goes on to say

> >* when I return to foreground in the first window ($ fg) the second

and fg is known and used, I presumed bg was too. I was curious if the 
effect he was seeing (assuming bg used) was related to the problem in the 
alpha series somewhere, where windows didn't appear to close correctly - 
hence asking the version he's using. Of course this is based on a lot of 
assumptions, and as a former collegue of mine was fond of saying "'Assume 
nothing!' should be tattooed on the inside of your eyelids". Second 
guessing our users calling the helpdesk at work can be amusing at times ;)

Regards, Martin
-- 
[EMAIL PROTECTED]  [EMAIL PROTECTED]  http://www.dbg400.net/"\
DBG/400 - DataBase Generation utilities - AS/400 / iSeries Open\ /
Source free test environment tools and others (file/spool/misc) X
Debian GNU/Linux | ASCII Ribbon Campaign against HTML mail & news  / \



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 from blackbox or anything else. what you need to do to send the 
process to the background is press ctrl-z and then type "bg", as martin 
illustrated in his example but didn't point out explicitly.

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 send the second to background
>* the second window "freezes" and cannot be killed or used
>* when I return to foreground in the first window ($ fg) the second
>one return to normal and resumes whatever was attempted (if kill was
>attempted, it finally dissapears).
>
>Is this normal?
>
>Ciprian Popovici
>
>  
>



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 the first window I press ctrl-z and send the second to background
>> * the second window "freezes" and cannot be killed or used
>> * when I return to foreground in the first window ($ fg) the second
>> one return to normal and resumes whatever was attempted (if kill was
>> attempted, it finally dissapears).
>> 
>> Is this normal?
> 
> Yes. When you hit that close button, it tells the app to close. When its
> stopped, it can't close until you resume it.
> 

To expound on this further.

When you stop the app, it can no longer process events.  The close button works
by sending a "I want you to close" message to the client from the wm.  The wm
has the choice to ignore or delay the closing.  For instance it may open a
"save open files" dialog.  When it woke up, the event was waiting in the queue.



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 ctrl-z and send the second to background
> * the second window "freezes" and cannot be killed or used
> * when I return to foreground in the first window ($ fg) the second
> one return to normal and resumes whatever was attempted (if kill was
> attempted, it finally dissapears).
> 
> Is this normal?

Yes. When you hit that close button, it tells the app to close. When its
stopped, it can't close until you resume it.

xOr
-- 
I am damn unsatisfied to be killed in this way.



msg07567/pgp0.pgp
Description: PGP signature


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 send the second to background
> * the second window "freezes" and cannot be killed or used
> * when I return to foreground in the first window ($ fg) the second
> one return to normal and resumes whatever was attempted (if kill was
> attempted, it finally dissapears).
>
> Is this normal?
>
> Ciprian Popovici

Which version is this? I don't see this behaviour in 0.65beta1 (well, cvs 
from Wednesday night). Using your recipe as below doesn't give me any 
problems.

Window 1
mrowe@jamaro:~$ aterm
[1]+  Stopped aterm
mrowe@jamaro:~$ bg
[1]+ aterm &
mrowe@jamaro:~$ 

Window 2
mrowe@jamaro:~$ which blackbox
/usr/local/bin/blackbox

Regards, Martin
-- 
[EMAIL PROTECTED]  [EMAIL PROTECTED]  http://www.dbg400.net/"\
DBG/400 - DataBase Generation utilities - AS/400 / iSeries Open\ /
Source free test environment tools and others (file/spool/misc) X
Debian GNU/Linux | ASCII Ribbon Campaign against HTML mail & news  / \