Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fish configuration #97

Open
cg505 opened this issue May 14, 2018 · 3 comments
Open

fish configuration #97

cg505 opened this issue May 14, 2018 · 3 comments

Comments

@cg505
Copy link
Contributor

cg505 commented May 14, 2018

This project intends to be a wide-ranging set of dotfiles. Currently it only contains emacs (although that's doing a pretty good job). As my primary shell, I use fish and hope to move the base of my configuration into this repo. Fish configuration doesn't really work in the same way emacs does in that you can configure it from the CLI instead of from mostly static config files (think set -U). I also use fisherman which work by creating symlinks into your config directory instead of creating a separate system that is loaded by your config (like in emacs with the elpa directory). These all pose challenges to a dot-style fish config that I am not sure how to solve. I don't even know if anyone else using this project also uses fish.

@rye
Copy link
Member

rye commented May 14, 2018

I'm surprised to hear that you use Fish as well, because I do too. And Fish is nice.

I don't do any package management in Fish and I don't know of any easy way of doing anything more than just symlinking files, I guess.

@rye
Copy link
Member

rye commented Jul 7, 2018

I will say that Fish makes it insanely easy to live-update your environment. If you make changes to a file in ~/.config/fish, it just magically happens. So, we could probably do some kind of stuff to get user configurations loaded.

@cg505
Copy link
Contributor Author

cg505 commented Jul 7, 2018

Thinking about this a bit, and I have a couple of thoughts:

  1. Treat .config/fish like .emacs.d and symlink in there. Viscously manage that directory.
  2. Place user config somewhere else (.config/dot/fish, for instance). Take care of symlinking things into .config/fish, or otherwise take care of letting fish know where to look for things.
  3. Eventually transition to a model where all user config is in .config/dot (including emacs user configs) which can be stored as username/.dot on github. Allows ultimate unification with emacs config wrt universally available personal configurations (which is the bestseller for this entire project, imo).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants