I'm running iTerm2. When do a text search ⌘ F, pressing Return moves the highlighted occurrence back (the previous occurrence). Is there a way to make it move to the next (forward) occurrence?
iTerm Text Search – Why iTerm Text Search is in Reverse Order
iterm
Related Solutions
Those hex codes are just sequences of bytes. For example mapping a key combination to 0x66 0x6f 0x6f would make it insert foo. 0xc3 0xa4 would insert ä if you use UTF-8. 0x1b 0x1b 0x5b 0x43 means escape escape [ C.
Some sequences of bytes like ANSI escape sequences and even single bytes like ASCII control characters have special meanings in terminals.
To make ⌘← and ⌘→ go to the beginning and end of line, you can assign them to 0x01 (^A in caret notation) and 0x05 (^E in caret notation):
- ⌘←: Send Hex Codes: 0x01
- ⌘→: Send Hex Codes: 0x05
You can make ⌥⌦ delete a word forward by assigning it to \ed:
- ⌥⌦: Send ^[ d
Changing ⌥← and ⌥→ to \eb and \ef in iTerm's preferences would also change them in programs that don't support readline or emacs-style keybindings. Another option is to add this to ~/.inputrc:
"\e\e[D": backward-word
"\e\e[C": forward-word
You can run read and press key combinations to see what characters they insert. For example ⌥← inserts ^[^[[D by default, where ^[ is escape in caret notation.
Here's a starting point.
In iTerm 2 go to Preferences > Profiles > (Your profile) > Advanced, then click Edit under Triggers.
Add a new Trigger using the + button at the bottom left, then set:
- Regular Expression:
.$ - Action:
Highlight Text… - Parameters:
Red on White(or a colour combination you find appropriately funkadelic)
Close the Triggers pane.
You should now see a white "line" at the far right of the iTerm window. This is really iTerm changing the last character on the line to red text on a white background. This should help you spot lines that are wrapped versus new lines.
Example screen grab below (I use fish shell, btw)…
Best Answer
Searching in reverse is apparently how iTerm's search works by design (see https://gitlab.com/gnachman/iterm2/issues/4491).
As a user, I also find this design decision confusing.
If you would like to make
Find Next/Find Previousin iTerm behave consistently with other apps, here are the proper keybinding overrides to add inSystem Preferences > Keyboard.Note that I had to restart iTerm for the keybindings to fully take effect.