Hello everyone,
I have reinstalled the midnight commander (mc) under kde and have been using it for years. Now I can’t use the F 10 key to close the mc. I can’t find the setting for it.
I don’t use Midnight Commander, but have you looked in System Settings / Keyboard / Shortcuts
to see if F10
(you can just type F10
in the search box) is assigned to some shortcut which interferes with Midnight Commander?
Indeed, Plasma now binds F10 for itself by default — I believe it’s bound to invoking the menu, albeit that I’m not sure — in Plasma 6. So one will need to unbind F10 as a Plasma shortcut in order to be able to use it for applications that have been hard-coded for that shortcut.
According to this topic: linux - Is there a way to change shortcuts in midnight commander? - Super User, all you need to do is the following:
cp /etc/mc/mc.keymap ~/.config/mc/
Then edit the key mappings of ~/.config/mc/mc.keymap
as you like and make sure you save it when done. Note that there are a lot of instances of f10
hotkeys in the file, but “Quit” should be on line 14 of the mc.keymap
file.
It might be Plasma’s “fault” - or it might be just specific to Konsole (the Terminal emulator).
But that is indeed the very first thing I take care of in every DE (I can’t live without mc) -
this also happens in Gnome Terminal and in Xfce4 Terminal, but the setting is more intuitive to find.
xfce4-terminal has got a menu item for it in the advanced settings tab
and so does gnome-terminal
Konsole works differently and I can’t remember where I found and changed that setting.
But I sure did.
As a work-around until you find it you can just install and use urxvt or plain xterm - it doesn’t happen there.
Thanks to everyone for the support, it works! I deactivated F10 in the system settings in kwin. Then I opened the console and assigned the F10 key to closing the window. But then the console wanted to close when I pressed the F10 key and the mc was still running. So I deleted the assignment of F10 to closing the window. After that, the mc could be closed with F10. However, I have no explanation for this process.
This sounds like the explanation to me.
Just unbind/disable the F10 - don’t assign it to something else.
Then mc
can have it and act as you’d expect.
I really don’t know why people like Plasma so much - to me there are far too many options and they are not at all intuitive to find.
(my personal opinion, of course)
They used to be, but the KDE developers, having been inspired by GNOME and Microsoft, decided to make it a bit more challenging for Plasma 6.
I don’t know about Microsoft (I don’t use it)
but as for inspired by Gnome:
at least the options are all accessible without special extensions in KDE/Plasma
In Gnome it’s even more of a nightmare still - and it changes all the time, too.
(in my experience)
I used to like Gnome - a long time ago.
Some, or even most people, might need it - I don’t
and am happily staying with Xfce4
Neither do I, but apparently most of the millennials at KDE do.
Case in point, the double-click instead of a single-click for opening files — which used to be the default — was taken over from Windows and GNOME, which itself also took that over from Windows.
I used to like Gnome - a long time ago.
Nah, I could never bring myself to liking it, and I really dislike gtk
.
Some, or even most people, might need it - I don’t
and am happily staying with Xfce4
Horses for courses, different strokes for different folks, and all that jazz.
Indeed, Plasma now binds F10 for itself by default
Yup, I’m quite comfortable with it by now - F10 also pulls down the Firefox menu (so no need to feel sad that it’s not in GlobalMenu).
With Hindsight, it’s one of the (annoying) changes in Plasma which I actually find to be very good.
Knee jerking isn’t always the best reaction.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.