The problem with ctrl-r is I've gotten used to NodeJS's retro-active ctrl-r (that's a slight misrepresentation). It's so clunky to have to realize after you start typing, oh, I should just search my history, then delete what you wrote, the ctrl-r, then retype. That sort of thing is what makes it 50:50 if it is better just to finish typing it out. IMO it should work with content already typed. That or we need a ctrl-up arrow to act like an up arrow that filters with what has already been typed.
In NodeJS's REPL the up arrow filters so you only get lines that start the same. But it has a similar impact as ctrl-r but less clunky. I think the ideal for both shell and Node REPL would be that, but match anywhere and not just the front like node does, and add the ability to select if you want that or a standard up arrow. So you would select one to be your main (I'd prefer matching) and then use ctrl to modify to the other.
Log in
This works if you are using zsh. I've never seen this in bash but maybe there is a way to configure it.
ctrl + r, youre welcome
The problem with ctrl-r is I've gotten used to NodeJS's retro-active ctrl-r (that's a slight misrepresentation). It's so clunky to have to realize after you start typing, oh, I should just search my history, then delete what you wrote, the ctrl-r, then retype. That sort of thing is what makes it 50:50 if it is better just to finish typing it out. IMO it should work with content already typed. That or we need a ctrl-up arrow to act like an up arrow that filters with what has already been typed.
In NodeJS's REPL the up arrow filters so you only get lines that start the same. But it has a similar impact as ctrl-r but less clunky. I think the ideal for both shell and Node REPL would be that, but match anywhere and not just the front like node does, and add the ability to select if you want that or a standard up arrow. So you would select one to be your main (I'd prefer matching) and then use ctrl to modify to the other.
One can dream.