search

doron-cohen / antidot

Cleans up your $HOME from those pesky dotfiles
MIT License
299 stars 18 forks source link

Antidot does not creaate fish env/alias files #225

Open NoelJacob opened 1 year ago

doron-cohen commented 1 year ago

Hey @NoelJacob . Could you elaborate on the steps you took and what was the effect? It's really hard to know what happened with such a short title.

NoelJacob commented 1 year ago

I did the exact proper usage and I only got bash files generated in the config folder

doron-cohen commented 1 year ago

Can you try running antidot init -s fish? I get this issue too. Working on a fix.

doron-cohen commented 1 year ago

The issue for me was that echo $SHELL was returning /bin/zsh instead of /usr/local/bin/fish. I believe this is caused since the terminal was running inside VSCode and it somehow messed up the environment variables.

NoelJacob commented 1 year ago

Mine was running in a normal fish terminal. Also if it had assumed the shell was zsh shouldn't it produce zsh files from json? Mine only created the default bash file. Same with and without -s fish flag.

NoelJacob commented 1 year ago

Also fish has some cooool built-ins to handle these cases. Set alias: set -gx VARIABLE value in fish.config or a file executed on every session https://stackoverflow.com/questions/25632846/how-to-set-environment-variables-in-fish-shell

Add to path: run once fish_add_path value https://fishshell.com/docs/current/cmds/fish_add_path.html

doron-cohen commented 1 year ago

Yes I know of these. I use fish and I enjoy it very much. I am working on changing the way antidot works. Hope it will make this issue irrelevant.