mcedit is now symlink to mc which causes subshell error to be displayed every time mcedit is run

Bug #1891750 reported by Gregor Snak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Midnight Commander
Fix Released
Unknown
mc (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

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)

Revision history for this message
Yury V. Zaytsev (zyv) wrote :

Fixed upstream in 4.8.25.

Changed in mc (Ubuntu):
status: New → Confirmed
Changed in mc:
status: Unknown → Fix Released
Revision history for this message
Gregor Snak (gsnak) wrote :

Awesome. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.