Apologies if this has been posted before, I found closed $PATH-related issues, but none that seemed fitting.
When I launch qutebrowser from the command line in MacOS the PATH includes everything I would expect and I'm able to correctly spawn mpv {url} and stuff like that. When I launch qutebrowser from the .app the PATH is extremely short and I can't spawn anything that's not built into the system.
I'm running 10.13.6 and installed qutebroswer with Homebrew.
PATH when launched from command line
PATH = /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/MacGPG2/bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/Users/jgillman/perl5/bin:/Users/jgillman/bin:/Users/jgillman/.dotfiles/bin:/usr/local/lib/node_modules:/Users/jgillman/node_modules/.bin:/Users/jgillman/.dotfiles/fzf/bin:/usr/local/sbin:/usr/local/opt/fzf/bin
PATH when lauched from .app
PATH = /usr/bin:/bin:/usr/sbin:/sbin
This all makes sense since launching it from the command line would inherit the environment from which it was launched, but it's annoying that it's not included when launched from the app. Not sure if that's a fixable thing, or if the solution is to always launch from the terminal.
Apologies if this has been posted before, I found closed $PATH-related issues, but none that seemed fitting.
When I launch qutebrowser from the command line in MacOS the PATH includes everything I would expect and I'm able to correctly
spawn mpv {url}and stuff like that. When I launch qutebrowser from the .app the PATH is extremely short and I can'tspawnanything that's not built into the system.I'm running 10.13.6 and installed qutebroswer with Homebrew.
PATH when launched from command line
PATH when lauched from .app
This all makes sense since launching it from the command line would inherit the environment from which it was launched, but it's annoying that it's not included when launched from the app. Not sure if that's a fixable thing, or if the solution is to always launch from the terminal.