#Warp won't recognize certain commands

3 messages · Page 1 of 1 (latest)

shadow dock
#

I have an issue with Warp that it won't recognize certain commands. When a command is typed, it's shown as white and linted, but executes fine. Some examples are nvim, pgcli and python framework commands like scrapy. In iterm2 I dont have this issue.

celest flaxBOT
#

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

#

Hmm, I don't know enough to give you a confident answer yet. However, based on the information from the extracts, it seems that Warp may sometimes have issues with recognizing certain commands, especially if they are part of a custom setup or if there are incompatibilities with certain tools or shell configurations.

One common suggestion for issues related to command recognition and compatibility in Warp is to check for incompatible tools and adjust your shell configuration accordingly. You can disable parts of your dotfiles just for Warp by using a conditional statement in your shell configuration files. Here's an example for Bash and Zsh:

if [[ $TERM_PROGRAM != "WarpTerminal" ]]; then
  # What you want to disable here
fi

And for Fish:

if test "$TERM_PROGRAM" != "WarpTerminal"
  # What you want to disable here
end

You can find a list of incompatible tools in the Warp documentation here (https://docs.warp.dev/help/known-issues#list-of-incompatible-tools).

If you continue to experience issues, it might be helpful to check the Warp GitHub Issues page for similar problems or to open a new issue for assistance.

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