#Usability: Long commands in History Command Search

4 messages · Page 1 of 1 (latest)

chrome kettle
#

Hi, I'm not sure if I'm missing something simple, but whenever I'm in the Command Search popup (Ctrl+R) looking for something, it's impossible to tell long commands from each other, because they are truncated.
Is there a way to see them before actually hitting Enter to paste them and do that again and again?
Thanks

image.png
hybrid kernelBOT
#

Hi @chrome kettle. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

You're right, this is a known limitation in Warp's Command Search functionality. Currently, long commands are truncated in the Command Search popup, making it difficult to distinguish between similar long commands. However, there are a few workarounds you can try:

  1. Expand the search panel: You can increase the width of the Command Search popup by dragging its edge with your mouse. This allows you to see more of the command GitHub Issue #2976 (https://github.com/warpdotdev/Warp/issues/2976).

  2. Use the UP arrow: After typing part of the command, press the UP arrow to see the full command in the input editor. You can then use UP/DOWN arrows to cycle through matching commands GitHub Issue #4597 (https://github.com/warpdotdev/Warp/issues/4597).

  3. Use the history command: You can run history | grep <your search term> to see the full commands in your history that match your search GitHub Issue #4597 (https://github.com/warpdotdev/Warp/issues/4597).

While these workarounds can help, they don't fully solve the issue of seeing the entire command directly in the Command Search popup. This limitation is acknowledged by the Warp team, and there are open GitHub issues tracking this problem, such as Issue #1405 (https://github.com/warpdotdev/Warp/issues/1405).

For now, you may need to use a combination of these workarounds to find the exact command you're looking for. The Warp team is aware of this usability issue, and you can follow the GitHub issues for updates on potential improvements to this feature.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@chrome kettle Kapa.ai is still learning and improving, please let me know how I did by reacting below.