Andy Koppe wrote:
Thomas Wolff:
Closing the terminal that a program was started from is not a completely
unrelated event,
this is also a matter of taste and use case but just using a command line to
*start* an application does not indicate the intent that the command line
should con
Thomas Wolff:
>> Closing the terminal that a program was started from is not a completely
>> unrelated event,
>
> this is also a matter of taste and use case but just using a command line to
> *start* an application does not indicate the intent that the command line
> should continue to *host* the
Andy Koppe wrote:
Thomas Wolff:
In general, a GUI application started in the background, like a terminal,
should detach itself from its parent process so that it survives if the
parent is terminated.
Says who?
Common practice in Unix/Linux/X environments.
I've fina
Andy Koppe:
> Thomas Wolff wrote:
>> In general, a GUI application started in the background, like a terminal,
>> should detach itself from its parent process so that it survives if the
>> parent is terminated.
>
> Says who? You can always invoke it with setsid or some such to detach it.
>
>> I've
Thomas Wolff:
> Termination of a terminal's parent. This should not abort the terminal
> session, whether or not the notification mechanism is HUP. (In the case
> console -> xterm you said it's due to console attachment, whatever that
> means in detail.)
Well, in practical terms it means that xter
Thomas Wolff:
>>> In general, a GUI application started in the background, like a terminal,
>>> should detach itself from its parent process so that it survives if the
>>> parent is terminated.
>>
>> Says who?
>
> Common practice in Unix/Linux/X environments.
I've finally got round to trying to co
On 04.03.2010 08:49, Andy Koppe wrote:
Thomas Wolff:
Andy Koppe:
Mintty has default handling for SIGHUP, i.e. it exits.
Actually (another topic but related) mintty has a great feature here: it
passed the SIGHUP to its client application and if that application catches
and han
Thomas Wolff:
> Andy Koppe:
>> Mintty has default handling for SIGHUP, i.e. it exits.
>
> Actually (another topic but related) mintty has a great feature here: it
> passed the SIGHUP to its client application and if that application catches
> and handles the SIGHUP, mintty does *not* exit.
I don't
On 26.02.2010 21:29, Andy Koppe wrote:
Thomas Wolff wrote:
In general, a GUI application started in the background, like a terminal,
should detach itself from its parent process so that it survives if the
parent is terminated.
Says who?
Common practice in Unix/Linux/X environments. An
Thomas Wolff wrote:
> In general, a GUI application started in the background, like a terminal,
> should detach itself from its parent process so that it survives if the
> parent is terminated.
Says who? You can always invoke it with setsid or some such to detach it.
> I've noticed the following
In general, a GUI application started in the background, like a terminal,
should detach itself from its parent process so that it survives if the
parent is terminated.
I've noticed the following sometimes surprising inconsistencies about this:
mintty
xterm &
mintty &
exit
11 matches
Mail list logo
