Ticket #3788 (new defect)
extension mechanism: signal in `View` process affects `Open` process
| Reported by: | yury_t | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | Future Releases |
| Component: | mc-core | Version: | master |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Branch state: | no branch | Votes for changeset: |
Description
Happens in 4.8.17-4.8.19, at least.
If the program launched to View (F3) some content type registered in extension file (e.g. lynx or links for html) is interrupted by Ctrl+C,
the program launched previously in background in the same mc instance to Open (ENTER) something is interrupted too. Even mplayer which normally ignores Ctrl+C.
Replication:
1) One or more Open actions. The Open action description must launch something into background and be long-running, like (mplayer %f &) on video or even just (xterm -e lynx %f &) on any type, just to sit and show the contents.
2) In the same mc instance -- View (F3) any local .html file, so lynx (or links) starts, interrupt it by Ctrl+C.
3) Both 'viewing' program and 'opening' program(s) (any number of instances) are terminated.
However,
a) If lynx or links is launched 'manually' in subshell and interrupted, it does not affect any running Open programs.
b) Does not happen between mc instances.
I wonder if this ever worked. If we have a good revision, then we can do bisect.