![]() ![]() It would be nice if you could then immediately re-press Ctrl+ h to execute, without having to Tab, then Enter.Īnd of course, switching replacement execution to a keybinding would then allow for a binding to advance backward after each replacement. ![]() The first press of Ctrl+ h re-opens the widget, with previous values still populating the find / replace fields. Probably more importantly, suppose you Esc out of the find widget entirely. Seems like it should be possible to execute without first switching back to the replace field. But what if you Tab back to the search field - maybe to update the search string? Both fields are populated. The shortcut is faster than moving your hands from the keyboard, highlighting with the mouse, right-clicking, selecting copy, and returning to the keyboard. Presently, you can only execute the replacement if you stay in that replace field, from where you can hit Enter. Input string to find, or accept string already present from prior find, or because it was highlighted when you entered the widget.The latter would replace and advance to the prior match. The former would replace and advance to the next match. "when": "editorFocus & findWidgetVisible".īoth would execute the replacement already entered into the find / replace fields, regardless of which of the fields in the find widget has focus. ![]() What I should have suggested is re-binding Ctrl+ h and Ctrl+ Shift+ h, with context. My last comment seems a bit off, in retrospect. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |