You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm big fan of autocomplete, have been using Ctrl + R quite frequently. I recently switched to fish. Even have it my .bashrc file.
It doesn't have the data from my previous shell. So, doesn't autocomplete yet. I think you guys can take the data from the history command?
The text was updated successfully, but these errors were encountered:
It's a good idea to import history from bash (and may be others shells too). But not all bash commands are valid fish commands. For e.g. 'export foo' is not valid in fish. We want to be as accurate as possible with our autosuggestions, and it's a different struggle to trasform (or may be ignore) invalid fish commands.
PS I have already done some work to import aliases, bash prompt and environment variables from bash. It's in import_config branch of our repository.
Instead of maintaining a list of commands which can not be imported from bash, may be we can just check whether a command is valid in fish. For e.g for builtins we can use builtin_exists() method
Hi,
I'm big fan of autocomplete, have been using Ctrl + R quite frequently. I recently switched to fish. Even have it my .bashrc file.
It doesn't have the data from my previous shell. So, doesn't autocomplete yet. I think you guys can take the data from the history command?
The text was updated successfully, but these errors were encountered: