History substring search

[cornerot]

Fish shell history search feature, where you can type in any part (not only by prefix) of any command from history and then press chosen keys, such as the UP and DOWN arrows, to cycle through matches.

[fdncred]

We do have $env.config.completion.algorithm that has prefix and fuzzy as options. Does this do what you're looking for?

[cornerot]

No. This option only affects commands autocompletion, not a history.
For example fish and nu behavior

[fdncred]

Hmmm, apparently we don't support this yet.

[cornerot]

It seems reedline issue

[sommerper]

Is there a way to do this with https://www.nushell.sh/book/line_editor.html#keybindings
Basically detecting arrow up / down and searching the history?

[sommerper]

It's true that the prefix search works - the issue is that - let's say I have previously written:
cat news.txt

... I can write cat in the prompt and use arrow up to scroll through all entries that have cat as the first part of the string.

But if I want to see all the history entries where I do something with news.txt, write that into the prompt, and press arrow up it will find nothing.

So it wont find something like:

touch news.txt
nano news.txt
cat news.txt

It's something that I do quiet often - but maybe I'm alone in doing that... =)

[fdncred]

With the default_config.nu, it seems like ctrl+r does this. There's also reverse serach with ctrl+q. I also have several history_menus in my config.nu.

[sommerper]

Yes, ctrl-q does exactly this.

I think what OP and I would like is that this is triggered on arrow up and down (with the current text in the prompt), without having to press ctrl-q first and then writing the text afterwards.

I often find myself having already typed the filename that I want to work with and then browse through the history.

It might seem a bit unnecessary but it is a slightly faster procedure if you know that what you're searching for is not that far back in history.

So this isn't a critique or anything but rather an optimization of sorts.

[fdncred]

ok, search in your config.nu and look for ctrl+q and change that to up. play around with the keybindings to see if you can get it working the way you want. keybindings list should show you what is available.

[sommerper]

I looked into it but I don't think I can do it without being able to execute custom commands.

If the prompt is empty it should just go one step up and down in history - but if something is already typed then it should switch to do a history substring search.

[MilesCranmer]

#12616

@cornerot @fdncred @sommerper