Description of problem:
Using mc with the -e argument, such as "mc -e somefile" brings you to the file browser instead of the editing interface even though the file exists in the current directory.
Version-Release number of selected component (if applicable):
Happens every time.
Steps to Reproduce:
1. Enter a terminal (through X or a tty)
2. Run mc -e somefile where somefile is an existing file (either exact or relative path)
mc opens up to the file browser as if you ran mc with no arguments
mc should open up the file editor as is the case when you run "mcedit somefile"
Thanks for bugreport. This was fixed in http://midnight-commander.org/ticket/2187
Jindrich, you may cherry-pick needed patch by command:
git diff 15fe01a..e14ddbd >mc-e.patch
and add it to exists 4.7.2 src.rpm.
Or just wait for next release (4.7.3 will released near the 5'th of July)
Slava, thanks for the quick action :)
I will wait for the next release and release update so that we can benefit from more fixes in 4.7.3. ... and I don't need to release updates twice ;)
Any ETA on this? It's hard to get used to using mcedit instead of mc -e after using mc -e for so many years. :-P
It is fixed by this update:
Just give it a positive karma so that it is pushed to stable repositories ASAP :)