1. 15
  1.  

  2. 3

    No need to copy pasta those dotfiles around anymore! fresh is a tool to source configuration (aliases, functions, etc) from others into your own shell files. We also support other files such as ackrc and gitconfig.

    Looking forward to hearing what you guys think of fresh. We’ve already got a bunch more features planned. See our list of upcoming features at http://github.com/freshshell/fresh/issues.

    1. 1

      what problem is this trying to solve?

      1. 3

        We found we were constantly copying bits and pieces of each others config files. We built this so we can easily share the pieces we need from each other. For instance @jasoncodes has his $EDITOR variable set up so it changes if you’re using tmux, instead of copying his code I used fresh to grab it.

        1. 3

          Interesting. Every so often I come across something I may want to add or change in one or another config file, but it happens so rarely that I can’t imagine wanting to involve Yet Another Tool to manage it. So this is interesting to me because you’re describing a behavior that sounds awfully foreign to me. :)

          “For instance @jasoncodes has his $EDITOR variable set up so it changes if you’re using tmux, instead of copying his code I used fresh to grab it.”

          But how often is that going to happen that using Fresh beats just pasting or typing some lines into a file? I guess often enough for you now, but don’t you expect that before long you’ll have some good, reliable, comfortable settings you don’t want to forever tweak?

          1. 2

            I’m often tweaking my dotfiles, my repo has over 500 commits. The other benefit is if something breaks (Git changes an options we’re using for instance) and @jasoncodes fixes it I can just update instead of making any changes manually. I guess it depends how often you tweak things. I work in an office where most people maintain their own set of dotfiles and if someone finds something new or a better way of doing things we can all benefit from it easily.

          2. 2

            The idea is cool, but how should I approach the discovering of new functionality (aliases, functions, etc)? Maybe there should be some central repository with information? Think web-interface with GitHub-repositories as a backend so it’s easy to discover and browse other people’s configuration.

            1. 2

              At the moment you can simply look through peoples dot files and grab what you want. Projects like Oh My Zsh are good because the functionality is broken up into small pieces that make it a perfect candidate for fresh. We were talking about this today, we’re thinking of setting up a wiki page that you can add to and we would scrape that an build a search into fresh so you can fresh search ackrc for instance and find all the ackrc files people have recommended.