Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

extension mechanism: signal in View process affects Open process #3788

Open
mc-butler opened this issue Mar 9, 2017 · 1 comment
Open

extension mechanism: signal in View process affects Open process #3788

mc-butler opened this issue Mar 9, 2017 · 1 comment
Labels
area: core Issues not related to a specific subsystem prio: medium Has the potential to affect progress

Comments

@mc-butler
Copy link

Important

This issue was migrated from Trac:

Origin https://midnight-commander.org/ticket/3788
Reporter yury_t

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.

@mc-butler
Copy link
Author

Changed by zaytsev-work (@zyv) on Mar 9, 2017 at 11:05 UTC (comment 1)

I wonder if this ever worked. If we have a good revision, then we can do bisect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: core Issues not related to a specific subsystem prio: medium Has the potential to affect progress
Development

No branches or pull requests

1 participant