clean up aliases

[Haroenv]

convert to functions:

I guess you know how to do basic translations like export to set -x in fish, and using regular functions instead of alias (although you could use alias in fish, too, but functions will perform faster due to fish lazy loading).

Functions should go into ~/.config/functions so that fish can lazy load them, which is faster than forcing the shell to run all of that at startup.

@bucaran

[ghost]

Good job and great start :+1:

I am a shell startup freak, so I would consider moving all those aliases to functions, just to save more milliseconds, but that's up to you. It will clutter up your ~/.config/fish/functions, so I see why one would hesitate too.

Notes

• fish has no concept of "private" functions, everything is global, for example, those functions you define inside fish_prompt will be created every time fish_prompt runs, i.e, every time. Nothing awful about that, as long as you give them a nice __my_thing-like prefix you will not run into anything ever.
• Consider using fisher i git_util for those functions you are creating inside your prompt.
• Also, be careful when committing your history file to GitHub, passwords or access tokens could creep in there easily.

[Haroenv]

ah that's a good point. I'll remove the history file.