Public bug reported:
When you run MC and then you try to run another MC from within already
running MC, it will show red error message because there can be only one
subshell per terminal. This is correct. Nobody wants to run MC from MC.
However before /usr/bin/mc and /usr/bin/mcedit were different programs,
so when you opened MC and then typed "mcedit /some/path/file.txt" it
didn't shown this error, which is correct. Now mcedit is symlink to mc,
so when I run "mcedit /some/path/file.txt" mc shows this error message
even tho it is no longer relevant, I'm not running mc but mcedit.
I think there was some detection code that understood that mcedit is not
mc but this detection code got lost somewhere.
It makes mcedit unusable from commandline as I need to dismiss pointless
error message every time.
Tested in Ubuntu 20.04.1 LTS
How to reproduce:
1. Run mc
2. Type "mcedit /etc/issue" (without quotes)
3. Red error will be displayed (this error is meant for MC, not for MCEDIT)
** Affects: mc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891750
Title:
mcedit is now symlink to mc which causes subshell error to be
displayed every time mcedit is run
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mc/+bug/1891750/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
