-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Quick view shortcut printed in menu, wrong shortcuts for File #1764
Comments
Replying to gotar (#1764):
Unconfirmed.
Unconfirmed.
Unconfirmed.
Unconfirmed.
Unconfirmed.
Unconfirmed.
But prefix "Gray" is correct for "Gray+", "Gray-" and "Gray*" shortcuts. |
I don't know how it is possible that your menu differs from mine, but "Gray" prefix although correct is simply not required as mentioned functions do work with plain [+-*]. |
Replying to gotar:
Me too. Are shortcuts correct in Command menu?
Ok, I'll remove "Gray" from shortcuts. |
Replying to gotar (#1764):
You are right. This default shortcut string is wrong. But it is occured if /etc/mc/mc.keymap file is absent. Fixed in 212_buttonbar_commands branch.
Also fixed in 212_buttonbar_commands branch. |
Yes, shortcuts are correct in Command menu and yes - I do all the checks with no configuration files, just plain mc binary. With mc.keymap menu indeed everything is correct. |
Replying to gotar:
This shortcut is present in MC code, but seems doesn't work very long time.
Great thanks!
But what about
|
You are welcome:)
I must have overlooked this one, it's on it's place.
And I've found similar things in editor: |
Replying to gotar:
Fixed in 212_buttonbar_commands branch. |
|
|
Important
This issue was migrated from Trac:
gotar
(gotar@….pl)Left/Right menu always had "Quick view C-x q" entry, now it's only "Quick view", while the shortcut was not changed and still works.
File manu contains wrong info for:
Delete F6 instead of F8
Select group M-* instead of just "+"
Unselect group Gray+ instead of just "-"
Reverse selection Gray- instead of "*"
and
Quick cd M-c
disappeared entirely.
The text was updated successfully, but these errors were encountered: