-
Notifications
You must be signed in to change notification settings - Fork 37
fid-kill autocomplete is broken #949
Copy link
Copy link
Open
Labels
bugUnexpected behaviorUnexpected behaviordeployed to `develop`Feature built. Currently BETA testing in the `develop` branchFeature built. Currently BETA testing in the `develop` branchin progressIssue is currently being worked on (possibly in a feature branch)Issue is currently being worked on (possibly in a feature branch)
Metadata
Metadata
Assignees
Labels
bugUnexpected behaviorUnexpected behaviordeployed to `develop`Feature built. Currently BETA testing in the `develop` branchFeature built. Currently BETA testing in the `develop` branchin progressIssue is currently being worked on (possibly in a feature branch)Issue is currently being worked on (possibly in a feature branch)
Describe the bug:
Write
fid-killPress Tab
Output resembles
Expected behaviour:
Proper autocomplete values. For example, the current implementation will always suggest
0first, which if I understand right is the shell process itself!Screenshots:
N/A
Platform (please complete the following information):
uname -aif supported: 6.16.10-arch1-1version --no-app-name: 7.0.2107Additional context
Attempted a fix via the following patch, which at least resulted in selectable output, but the commands run during the autocomplete function itself were also present, cluttering the output. If I open helix and suspend it, when I run
fid-killand tab with my patch applied there are 8 results, when really I'm only interested in the one I manually suspended.Maybe this is unavoidable though? I can't think of a non-brittle way to filter them out.
Patch: