withfig / fig

Public issue tracker for Fig.
https://fig.io
MIT License
2.05k stars 63 forks source link

Need to run `fig source` for every shell session #430

Closed fwesss closed 2 years ago

fwesss commented 3 years ago

Sanity checks

Issue Details

Description:

Every time I open a new terminal window, tab, or pane, I need to run fig source for Fig to work.

Environment

Version 1.0.47 (B257) [U.S.]
UserShell: /bin/zsh
Bundle path: /Applications/Fig.app
Autocomplete: true
Settings.json: true
CLI installed: true
CLI tool path: /Users/maximekhoy/.fig/bin/fig
Accessibility: true
Number of specs: 190
SSH Integration: false
Tmux Integration: true
Keybindings path: /Users/maximekhoy/.fig/user/keybindings
iTerm Integration: true [Authenticated]
Hyper Integration: false
VSCode Integration: true
Docker Integration: true
Symlinked dotfiles: false
Only insert on tab: false
Installation Script: true
PseudoTerminal Path: /Users/maximekhoy/platform-tools:/Users/maximekhoy/.yarn/bin:/Users/maximekhoy/.config/yarn/global/node_modules/.bin:/Users/maximekhoy/.nvm/versions/node/v14.15.4/bin:/Users/maximekhoy/.cargo/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin:/Library/Apple/bin:/opt/X11/bin:/Users/maximekhoy/.fig/bin:/usr/local/bin:/Users/maximekhoy/.deno/bin:/usr/local/bin/python3:/usr/local/opt/fzf/bin
SecureKeyboardInput: false
SecureKeyboardProcess: <none>
Current active process: /bin/zsh (10244) - ttys023
Current working directory: /Users/maximekhoy
Current window identifier: 540355/BD3B1856-79E8-46EF-B69C-18508DFFDCFD% (com.googlecode.iterm2)
PATH: /Users/maximekhoy/platform-tools:/Users/maximekhoy/.yarn/bin:/Users/maximekhoy/.config/yarn/global/node_modules/.bin:/Users/maximekhoy/.nvm/versions/node/v14.15.4/bin:/Users/maximekhoy/.cargo/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin:/Library/Apple/bin:/opt/X11/bin:/Users/maximekhoy/.fig/bin:/usr/local/bin:/Users/maximekhoy/.deno/bin:/usr/local/bin/python3:/usr/local/opt/fzf/bin
FIG_INTEGRATION_VERSION: 4
mschrage commented 2 years ago

This behavior is a bug. It should no longer exist.