fig
fig copied to clipboard
bug:
Checks
- [X] I have searched github.com/withfig/fig/issues and there are no duplicates of my issue
- [X] I have run
fig doctorin the affected terminal session - [X] I have run
fig restartand replicated the issue again
Operating system
Ventura
Expected behaviour
Fig sometimes randomly breaks breaking autocomplete for some commands like cat
It mostly seems to affect completing fs path, apart from that sub commands work fine
This fixes it when it breaks
sudo rm -rf ~/.local/bin/fig ~/.fig/history ~/.fig/logs
Actual behaviour
.
Steps to reproduce
No response
Environment
fig-details:
- 2.17.1
hardware-info:
- model:
- model-id:
- chip-id: Apple M1 Max
- cores: 10
- mem: 32.00 GB
os-info:
- macOS 14.0.0 (23A344)
environment:
- shell: /bin/zsh
- terminal: terminal
- cwd: /Users/neo/Desktop/lighthouse
- exe-path: /opt/homebrew/bin/fig
- install-method: brew
- env-vars:
- FIGTERM_SESSION_ID: 8f3486b8-dfa1-48fb-99d3-8cd7cc19bb4e
- FIG_SET_PARENT_CHECK: 1
- FIG_TERM: 2.17.1
- PATH: /Users/neo/.local/share/fig/plugins/git-open:/opt/homebrew/opt/[email protected]/sbin:/opt/homebrew/opt/[email protected]/bin:/Users/neo/.deno/bin:/Users/neo/.pyenv/shims:/Users/neo/.bun/bin:/Users/neo/.nvm/versions/node/v21.6.1/bin:/Users/neo/.rbenv/shims:/opt/homebrew/opt/ruby/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Library/Apple/usr/bin:/usr/local/go/bin:/Users/neo/.cargo/bin:/Users/neo/.fig/bin:/Users/neo/.local/bin:/Users/neo/.orbstack/bin:/bin:/Users/neo/go/bin:/Users/neo/Library/Android/sdk/platform-tools
- SHELL: /bin/zsh
- TERM: xterm-256color
- __CFBundleIdentifier: com.apple.Terminal
- FIG_PID: 80178
- FIG_SET_PARENT: 8f3486b8-dfa1-48fb-99d3-8cd7cc19bb4e
That is strange, could you next time that happens check what the history file looks like at the end.
@grant0417 DMed you the all the logs on Discord