Unverified50% confidenceCautionExact time
When using basename in a batch processing loop, variables must be wrapped in double quotes if the path or filename contains spaces; otherwise, the shell will misinterpret spaces as argument separators, causing the script to fail.
1
Sources
50%
Confidence
Long-term
Relevance
9/16/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedRunning basename directly without any arguments returns an error; it must receive a file or directory path as an argument.68% similarUnverifiedThe parameter expansion syntax ${path##*/} built into Bash and Zsh can achieve the same effect as basename and eliminates subprocess overhead in loop scenarios.68% similarUnverifiedRules under the .claude/rules directory without a Path configuration are loaded unconditionally, while rules with a Path configuration are only loaded when operating on matching files.61% similarUnverifiedOn Unix/Mac systems, NVM is implemented through a shell function that modifies the PATH variable in the current shell session58% similarUnverifiedThe "not recognized as an internal or external command" error when executing the claude command is caused by the installation path not being added to the system PATH environment variable.58% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/925270API
curl https://kongchang.com/api/v1/knowledge/claims/925270MCP
get_claim(id=925270)