Not sure what the command palette is, think I used the second method via Plugins/Options editor lite.
Seems a bit strange to have to specify it in two separate places though? Could you change it to make this easier to use?
Live for an ideal and leave no place in the mind for anything else.
1- Cmd Palette is a dialog: call it by 'Help / Command Palette'.
F9 key there allows to change hotkeys.
but Cmd Palette don't have 'Replace next' item so we cannot change Replace hotkey there.
so - we have only 1 way to change Replace hotkey.
2- attach in zip your user.json + keys.json files. so I can try to repeat the issue.
3- since Cmd Palette don't have 'Replace next' item - editor cannot react to F4 (you assigned it via Options Editor) when editor is focused. this is by design! only focused find-dialog can react to F4.
Seems I got what is your problem.
you put focus to editor and want that F4 replaces next word.
but Cud don't support F4 key in editor! it needs focus in the find-dialog input field.
so click on input field in find-dlg before pressing F4.
F3 is different story. editor supports such command in the Cmd Palette so F3 works when editor is focused.
Ok, so why doesn't the editor support F4?
Tbh, I only used F4 as it was next to F3 so it made it physically easier to use that key when doing a lot of replacing.
Live for an ideal and leave no place in the mind for anything else.
I think I see what you mean about why it doesn't work.
So, I suppose it comes down to a feature request!
Could you add 'Replace next' item to the cmd palette? Or is it something you don't wish to do?
Live for an ideal and leave no place in the mind for anything else.
+ add: added Command Palette item "find next and replace"
* change: deleted options "find_hotkey_find_next", "find_hotkey_replace", now usual Command Palette hotkeys are used here
(options are deleted in new default.json which you can download in our Github)