G
G
gpfspam2018-09-01 20:50:45
Debian
gpfspam, 2018-09-01 20:50:45

Midnight Commander why does the W key erase a line and not write a letter?

version MC 4.8.18-1
Debian GNU/Linux 9.5 (stretch)
I see a glitch, I try to type the character w, instead of a letter, it erases the characters to the left of the cursor before the beginning of the line,
reinstalled mc, it did not help.
I noticed that under root there is only such a jamb, under another user w prints normally.
I'm starting to compare users' home directories ~/.config/mc/. There is no mc.keymap file anywhere. I compared the ini files, they are the same, but there is also no keymap parameter in the [Midnight-Commander] section.
I watch the environment variable echo $MC_KEYMAP, under any user, empty.
I looked in /etc/mc/ there are three files with the .keymap extension:
mc.default.keymap
mc.emacs.keymap
mc.keymap
I try to start the MS with the keys:
mc -K /etc/mc/mc.default.keymap
mc -K /etc/mc/mc.emacs.keymap
mc -K /etc/mc/mc.keymap
mc --keymap=/etc/mc/mc.default .keymap
mc --keymap=/etc/mc/mc.emacs.keymap
mc --keymap=/etc/mc/mc.keymap
unchanged.
And finally, there are no files with the .keymap extension in /usr/share/mc/
Why is everything fine under another user, where does he pull the correct .keymap from, if it's all the same?

Answer the question

In order to leave comments, you need to log in

3 answer(s)
S
Saiputdin Omarov, 2018-09-01
@generalx

That's right, the problem is with CTRL. It can be either left or right.

G
gpfspam, 2018-09-02
@gpfspam

There can be no mechanical sticking of the key, because. I work remotely from different keyboards.
On the command line itself, the letter prints normally.
Here the problem is in the MC itself, let's say Ctrl sticks somehow programmatically, but other combinations work out correctly:
Ctrl-U cancel the last action Ctrl
-K delete to the end of the line from the current cursor position Ctrl
-Y delete the line
Ctrl-Z go to the beginning previous word
Ctrl-X go to end of next word

K
krypt3r, 2018-09-03
@krypt3r

Has this already been checked?
Redefining keyboard commands
Keyboard commands can be read from an external file. First, Midnight Commander creates a map of keyboard commands from the list defined in the
source code. Then the two files /etc/mc/mc.keymap and /usr/share/mc/mc.keymap are always loaded, sequentially overriding the previously loaded commands.
The search for a user-defined keymap file is performed according to the following algorithm (until the file is first found):
1) command line parameter -K <file> or --keymap=<file>
2) MC_KEYMAP environment variable
3) keymap parameter in the [Midnight] section -Commander] configuration file.
4) file ~/.config/mc/mc.keymap
The parameters in the first three cases may contain an absolute path to the keyboard command file or simply the name of the binding scheme (with or
without the .keymap extension). In this case, the search for the keyboard commands file will occur in the following directories (until the first location):
1) ~/.config/mc/
2) /etc/mc/
3) /usr/share/mc/

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question