grand jewel
When entering a multi line command in fish, eg:
for f in *
echo file $f
end
I can't get all the lines back when I up arrow through history to that command.
Also, my old fish history, before I started using warp, gets \ characters after each line in a multi line entry as of its trying to treat those as bash commands.
blissful scarabBOT
Hi @grand jewel. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
Based on the information provided in the extracts, it seems that there are some known issues with the Fish shell's history navigation in Warp.
In the Github Issue 849 (https://github.com/warpdotdev/Warp/issues/849), a user mentioned that Fish does history searching a little differently from most shells' Ctrl+R. In Terminal.app, they can type a substring of a previous command, hit the up arrow, and recall the command. However, in Warp, they can only type the beginning substring of a command and hit the up arrow.
In Github Issue 189 (https://github.com/warpdotdev/Warp/issues/189), a user requested an escape sequence for multiline editing for historical commands. They mentioned that if they populate the input editor with a prior command that was multiline, they're not able to move their cursor up in the multiline since cursor up -> the previous command from history.
As for the issue with your old Fish history getting \ characters after each line in a multi-line entry, it's not mentioned in the provided extracts.