Fish is appealing to me, though I haven’t invested any time in linking a somewhat extensive set of bash functions, aliases, etc. But sometimes it is nice to drop down into it when working with many files of uncertain names and so on. Do you do much with fish_variables, etc? The documentation seems quite oblique.
Whether people use fish as a main shell or a tool perform certain types of activities is not entirely clear to me. But in my bashrc I have several search functions, timestamps aliases which I find myself inadvertently calling from fish. I could port them over to fish_variables and such, but I don’t really want to maintain two sets of shell customisations. Another example is if you accidentally try to activate a vitualenv … I suspect it is not really meant to be a main shell, but thats why I asked.
deleted by creator
Fish is appealing to me, though I haven’t invested any time in linking a somewhat extensive set of bash functions, aliases, etc. But sometimes it is nice to drop down into it when working with many files of uncertain names and so on. Do you do much with fish_variables, etc? The documentation seems quite oblique.
deleted by creator
Whether people use fish as a main shell or a tool perform certain types of activities is not entirely clear to me. But in my bashrc I have several search functions, timestamps aliases which I find myself inadvertently calling from fish. I could port them over to fish_variables and such, but I don’t really want to maintain two sets of shell customisations. Another example is if you accidentally try to activate a vitualenv … I suspect it is not really meant to be a main shell, but thats why I asked.
you can get the best of both worlds with zsh and zsh-autosuggestions
deleted by creator