Open Issues Need Help
View All on GitHub good first issue
text interactively given to read appears in history 3 months ago
good first issue
good first issue
Option to make `git rebase --interactive` show commits completion before/instead of branch completion 4 months ago
good first issue
funced saves to wrong file for copied functions 4 months ago
good first issue
good first issue
docs: undocumented functions 4 months ago
docs good first issue
Add `SHELL_PROMPT_PREFIX` et al to default prompts 4 months ago
enhancement good first issue
good first issue
Please allow `|&` 4 months ago
good first issue
`backward-word-end` crashes 4 months ago
good first issue
vi mode: support Vim redo/readline's `vi-redo` 4 months ago
enhancement vi-mode good first issue
fish_indent: some comments are deleted 4 months ago
good first issue
When using `bind` to query existing bindings, show results from all modes unless a --mode argument is specified 6 months ago
good first issue
Git autocomplete for "git stash" missing 7 months ago
question good first issue
good first issue
good first issue
dnf completions lack config-manager subcommand 7 months ago
enhancement completions good first issue
completions good first issue
good first issue
Request: CUA-mode keybindings 7 months ago
good first issue
unable to autocomplete by flatpak app name 7 months ago
good first issue
Interactive fish requires ctrl-C to become usable 7 months ago
good first issue
Shell completion for git toggle arguments incomplete 7 months ago
good first issue
Certain Hledger autocompletions are deprecated 7 months ago
good first issue
good first issue
*-kill-path-component broken for paths with spaces 7 months ago
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.
Complexity:
2/5
bug good first issue
good first issue
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.
Complexity:
3/5
bug good first issue
good first issue
good first issue
Command name exceeding maximum file name size is reported by fish as existing but not executable 9 months ago
good first issue
String split fields negative indexing 9 months ago
good first issue