src_keybindC_mistakes

[vit_r]

By the way

Is this line (src/keybind.c: 669) correct:

{ XCTRL ('@'), CK_SingleDirsizeCmd, "C-Space" },

And these:
const global_keymap_t default_viewer_keymap[] = {

{ 'h', CK_ViewMoveLeft, "h" },
{ KEY_LEFT, CK_ViewMoveLeft, "Left" },

{ 'l', CK_ViewMoveRight, "l" },
{ KEY_RIGHT, CK_ViewMoveRight, "Right" },

{ 'r', CK_ViewNewBookmark, "r" },

may have a more logical look, for example :

{ 'l', CK_ViewMoveLeft, "l" },
{ KEY_LEFT, CK_ViewMoveLeft, "Left" },

{ 'r', CK_ViewMoveRight, "r" },
{ KEY_RIGHT, CK_ViewMoveRight, "Right" },

{ 'n', CK_ViewNewBookmark, "n" },

because when

'l' is CK_...Right

it puzzles, but may be some deeper reasons ... ?

[andrew_b]

attachment 1824-src_keybindC_mistakes.patch added

Thanks! Fixed in 212_buttonbar_commands branch.

[vit_r]

Replying to andrew_b:

attachment 1824-src_keybindC_mistakes.patch added

Thanks! Fixed in 212_buttonbar_commands branch.

You mean my msg has something new ?
And when 212_* will be merged to 'master' ?
For example edit.c has a lot of declarations to be corrected
like int line -> long line
but may be they are fixed already ?
The question is:
Where are fixings gathered ?

Excuse me for ignorance

Vit

[andrew_b]

Replying to vit_r:

Replying to andrew_b:
You mean my msg has something new ?

Yes.

And when 212_* will be merged to 'master' ?

When #212 will get the second vote from one of MC developers.

For example edit.c has a lot of declarations to be corrected
like int line -> long line
but may be they are fixed already ?

No. That fixes require new ticket.

The question is:
Where are fixings gathered ?

One ticket is for one fix (or several related fixes).

[vit_r]

Ohh ...
Great: its much more clear
Big-big THANKS

That fixes

some are on the way right now

[angel_il]

802 { KEY_F (8), CK_DeleteCmd, "F6" },

already fixed in 'master'