Ticket #3074 (new enhancement)

Opened 10 years ago

Last modified 10 years ago

Quitting mc shouldn't quit its children

Reported by: dnied Owned by:
Priority: major Milestone: Future Releases
Component: mc-core Version: 4.8.8
Keywords: fork,kill,window,destroy Cc: gotar@…
Blocked By: Blocking:
Branch state: no branch Votes for changeset:


Sometimes I would like to use MC to launch an appropriate app for a document (e.g.: xpdf) and then quit MC without having its child xpdf (or whatever) quit as well.

Also, I think MC should be made to exit cleanly when xterm's window is killed, just like any GUI file manager would quit upon window closing.

Basically, with these 2 enhancements, MC could work as a drop-in replacement for any graphical file manager, which is one way I'd like to use it.

Change History

comment:1 Changed 10 years ago by ossi

the launched app terminates because the pts created by mc is torn down and the app gets SIGHUP. on the command line it is your responsibility to use the nohup command to avoid this. for the viewers/editors mc automatically launches, suppressing SIGHUP is a reasonable request. even completely detaching the viewers from the terminal may make sense.

when the parent terminal is closed, mc could at best react to the SIGHUP it gets and do some kind of emergency cleanup. that's kinda far off from a "clean exit", though.

i posted some requests for improving x11 integration a long time ago (some of the earliest reports here). use the search function.

comment:2 Changed 10 years ago by gotar

  • Cc gotar@… added
Note: See TracTickets for help on using tickets.