Open Issues Need Help
View All on GitHubThe user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
AI Summary: The `backward-kill-path-component` command (`Ctrl+W`) incorrectly deletes only a portion of a path component when it contains spaces and is escaped. Instead of removing the entire component (e.g., `I\ am\ a\ file`), it only deletes the last word (e.g., `file`), which is not the expected behavior for a path component.
The user-friendly command line shell.
The user-friendly command line shell.
AI Summary: The issue describes a bug where tab-completion fails to properly escape commas when generating file paths within brace expansions. This leads to incorrect command arguments, as the shell interprets the unescaped commas as delimiters, resulting in "No such file or directory" errors for files containing commas in their names.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.
The user-friendly command line shell.