Shell auto completion
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 65.1k
- Forks
- 5.6k
- PR merge metrics
- PR metrics pending
Description
Discord username (optional)
No response
Describe the bug
When using source script.sh to make my bash functions available in the current session I am not able to get them in auto completion.
To reproduce
- Create a script file with a function but dont execute it in the function itself
- use source scriptfile
- try using auto completion for the function name it doesnt work
Expected behavior
No response
Screenshots
No response
Operating system
MacOS
Operating system and version
Sonoma
Shell Version
No response
Current Warp version
No response
Regression
Yes, this bug started recently or with an X Warp version
Recent working Warp date
No response
Additional context
No response
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)
Yes, this I confirmed this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the mentioned script.sh or scriptfile on macOS: define a function, source the file, and try completing its name in Warp. Compare the same sourced function in another terminal, then verify that sourced bash functions receive autocomplete in Warp.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, macos
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100