Skip to content
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

Hot-key override data when attempt to add new field in Listenig mode #2431

Closed
mc-butler opened this issue Nov 25, 2010 · 2 comments
Closed
Labels
area: core Issues not related to a specific subsystem prio: medium Has the potential to affect progress res: invalid The ticket is not a bug, or is a support request

Comments

@mc-butler
Copy link

Important

This issue was migrated from Trac:

Origin https://midnight-commander.org/ticket/2431
Reporter AlexJ

That is impossible to enter 'group' field in the user mini status record.

How to repeat:
F9 -> Listening mode
Select "Full mode", check "User mini status" and try to add custom field, for example:
half type name| owner | group | size | perm

when you will type character 'u' in the word 'group' cursor always move to "User defined field" record because of "u" is the hot-key for that record instead of "U".
Even if you prepare somewhere else the whole string:
'half type name| owner | group | size | perm '
and will attempt to paste it - anyway parser will catch character 'u' and move cursor out of "User mini status" record.

Suggestion:
Override hot-key 'u' to "U"

The only one possibility to enter configuration field string now is to shutdown MC, go to the ~/.mc and edit file 'panel.ini' with any editor.

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Nov 26, 2010 at 5:50 UTC (comment 1)

  • Version 4.7.4 deleted
  • Resolution set to invalid
  • Milestone 4.7 deleted
  • Status changed from new to closed

This is already fixed in #2405. Please use search before create new tickets.

@mc-butler
Copy link
Author

Changed by AlexJ on Nov 26, 2010 at 13:30 UTC (comment 1.2)

Replying to andrew_b:

This is already fixed in #2405. Please use search before create new tickets.

I tried to search it, but... my bad, sorry I guess I used wrong keywords for search terms that's why I didn't found it.

Thanks for fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: core Issues not related to a specific subsystem prio: medium Has the potential to affect progress res: invalid The ticket is not a bug, or is a support request
Development

No branches or pull requests

1 participant