Sometimes it would be useful to use a non-github repo. For example there are some git commands I have got from an account on gitorious, but fresh can't deal with that. With my previous hacked together solution I used a git submodule, but fresh is definitely a nicer way to do this.

I would leave the existing syntax alone. But if a full git URL was given, then fresh should use it as such. This is the way that vundle vim bundle manager) works and it seems like a good way to go for me.

Thanks for a great tool.

When sourcing different versions of the same file, it'd be great if it added a comment to show where each version starts, e.g.

# ~/.freshrc
fresh jasoncodes/dotfiles tmux.conf --file
fresh twe4ked/dotfiles config/tmux.conf --file

# ~/.tmux.conf

# source: jasoncodes/dotfiles/tmux.conf
...
...

# source: twe4ked/dotfiles/config/tmux.conf
...
...

Right now if you run fresh update on a secondary machine, your ~/.dotfiles repo is not automatically updated. This results in needing to do things such as cd ~/.dotfiles && git pull --rebase && fresh update instead.

I think fresh update without parameters should update ~/.dotfiles as well everything in ~/.fresh/source.

Ideally there should be a way to just update ~/.dotfiles without updating other repos too. I’d be fine with something like --local.

Perhaps include a full description of the available DSL. Can we have fresh itself contain this rather than the install script?

With dotfiles moving around it’s easy for entries in the Directory to become out of date. We should have a script which verifies every fresh line loads and every URL is reachable.

This could be implemented as a utility script in the fresh repo which retrieves all entries from the fresh API, builds up a test freshrc, runs fresh in isolation, and then curl -sLIs every URL to ensure they load.

Explain what fresh does with a ~./freshrc example.

In order to DRY up fresh lines with repeated options we need a way to set options for multiple lines.

fresh-options --file=~/.vimrc --marker=\"
  fresh vim/leader.vim
  fresh vim/vundle_before.vim
  fresh vim/vundle.vim
  fresh vim/vundle_after.vim
  fresh vim/functions.vim
  fresh vim/keybindings.vim
  fresh vim/plugin_config/\*
  fresh vim/vimrc
  fresh hackling/dotfiles vim/keybindings/numpad.vim
fresh-options # reset

fresh vim/gvimrc --file
fresh vim/colors --file=~/.vim/colors/

If the user/dotfiles is cloned to ~/.dotfiles, these files can be referenced in ~/.freshrc by omitting the repo name.
In this case there is no need to specify user/dotfiles. In fact, if you do, fresh will clone the repo again and you’ll have to push your changes before they’re available to fresh.

We should output a warning when fresh runs if ~/.dotfiles is a clone of a repo specified in ~/.freshrc.

Ideally this warning should include a corrected fresh line. There should also be a way to supress the warning (like FRESH_NO_BIN_CHECK).

Hi Again,

Today I put fresh to the test and cloned my dot files at work.
Except I didn't because the following happened:

bash -c "`curl -sL get.freshshell.com`"
Initialized empty Git repository in /home/marks/.fresh/source/freshshell/fresh/.
git/
remote: Counting objects: 856, done.
remote: Compressing objects: 100% (359/359), done.
remote: Total 856 (delta 446), reused 793 (delta 383)
Receiving objects: 100% (856/856), 154.55 KiB, done.
Resolving deltas: 100% (446/446), done.
Your dot files are now fresh.

  __               _
 / _|             | |
| |_ _ __ ___  ___| |__
|  _| '__/ _ \\/ __| '_ \\
| | | | |  __/\\__ \\ | | |
|_| |_|  \\___||___/_| |_|
http://freshshell.com/

You're all ready to get fresh!

Add `source ~/.fresh/build/shell.sh` to your shell config.

Open a new shell, run `fresh edit` to start editing your .freshrc file
then run `fresh` to update your shell.

$ cat .freshrc
# freshshell.com
#
# Examples:
#
#   fresh twe4ked/dotfiles shell/functions.sh
#   fresh jasoncodes/dotfiles aliases/rails.sh
#   fresh jasoncodes/dotfiles config/tmux.conf --file
#
# See http://freshshell.com/readme for documentation.

# Fresh
fresh freshshell/fresh bin/fresh --bin

# All dotfiles into ~
fresh config/* --file

# Freemind config (could also add the custom icons here maybe)
fresh freemind/user.properties --file=~/.freemind/user.properties

# Do all the bin files into ~/bin at once, mwahaha
fresh bin --bin

# Mutt config all lives in .mutt
fresh mutt --file=~/.mutt/

$ fresh
rm: cannot remove directory `/home/marks/.fresh/build/bin': Directory not empty

Any idea what's going on here?

.freshrc is not empty because I first cloned my .dotfiles repo under ~/ and symlinked linked ~/.freshrc to ~/.dotfiles/freshrc.

I had omitted to source shell.sh but adding that doesn't change the above behaviour.
After doing the curl, my dot files are working, but after running fresh, fresh tries to delete itself.
Am I missing a trick, or have I unearthed something?

Is it possible to specify specific files to be installed as sudo, but still have all the file references relative to the current user's homedir?

As the fresh ecosystem grows we may source a lot more (trusted?) upstream files.
Perhaps we might consider supporting a common repository target as an option to fresh-options.

Example usage

# Default the repo for the following lines
fresh-options --repo=twe4ked/dotfiles --file=~/.zshrc --marker  
  fresh zsh/completion.zsh

  # Preserve access to local context by overriding repo to empty
  fresh zsh/my_completions.zsh --repo='' 

  # Honour the original syntax for different (non-local) repos
  fresh freshshell/fresh contrib/source-build.sh  

  # ...

  fresh zsh/prompt.zsh --ref=7192f1a
fresh-options 

Right now we see an error like Could not find "pryrc" source file.
which does not actually mention which freshrc line is at fault.

We should probably also suggest fresh update and link to the source repo.

At the moment it's hard to tell if a command fails.

Idea at the moment is to simply make the existing success and error messages green and red respectively.

Tell the user they can now fresh edit then fresh.

When concaternating files, fresh makes a assumption that the file's basename is unique.

Therefore, when I use something similar to this:

fresh config/newsbeuter/config --file=~/.config/newsbeuter/config
fresh config/ncmpcpp/config --file=~/.ncmpcpp/config

The two files are merged, as they both have the basename 'config'.

Add ability to pull remote files from GitHub.

# ~/.freshrc
fresh jasoncodes/dotfiles aliases/git
fresh twe4ked/dotfiles aliases/ruby

fresh clean

1. Scan home directory and ~/bin for dead symlinks into ~/.fresh/build and remove them.
2. Remove repos from ~/.fresh/source which are no longer referenced by ~/.freshrc.

fresh aliases/git should try aliases/git and then aliases/git.sh.

# ~/.freshrc
fresh jasoncodes/scripts sedmv --bin # ~/bin/sedmv
fresh jasoncodes/scripts gemdiff --bin=~/bin/diff-gems
fresh jasoncodes/fresh bin/fresh --bin

Extension on #3.

At the moment we only check that symlinks exist. We should make sure they point to the correct path.

Make it easier to see the compare URLs, that's all I care about.

One can fairly easy end up creating a bad script if one is sourcing bin files from multiple locations.

We should emit a warning if this happens and have an option to supress said warning.

Hi, I'm enjoying freshening up my dotfiles!

I want to put my .msmtprc into my dotfiles repo.

That's ok, but then they end up in ~/.fresh/build/ as -r--r--r-- and msmtp complains that the config file must have no more than user read/write permissions. Not a Git expert, perhaps there is a way to specify this in git, though not all file systems support it -- anyway the only think I've seen is using git hooks to execute chmod. What would you recommend?
Thanks

Mark

# from the #freshshell IRC.
[07:37:36] @jasoncodes: install script idea: set an environment variable for install.sh to do the clone for you
[07:38:27] @jasoncodes: DOTFILES=jasoncodes/dotfiles bash -c "`curl -sL get.freshshell.com`"

Thinking the variable should be less generic. Perhaps FRESH_LOCAL_SOURCE.

The idea is so you can run a single fresh install line to install your entire config.

It would be useful to have an easy way to see the contents of the files that I am including.

eg. fresh show

If a user runs fresh twe4ked/dotfiles bin/psg --bin from the command line we should detect the / and ask if the user wants the line appended to their freshrc.

Currently:

ln: /Users/odin/.pryrc: File exists

# .freshrc
fresh twe4ked/dotfiles fresh/zsh-syntax-highlighting.freshrc --freshrc

…could be used to pull in this zsh syntax highlighting freshrc:

# fresh/zsh-syntax-highlighting.freshrc
fresh zsh-users/zsh-syntax-highlighting zsh-syntax-highlighting.zsh --file=vendor/zsh-syntax-highlighting.zsh
fresh zsh-users/zsh-syntax-highlighting highlighters/main/main-highlighter.zsh --file=vendor/highlighters/main/main-highlighter.zsh
fresh zsh-users/zsh-syntax-highlighting highlighters/brackets/brackets-highlighter.zsh --file=vendor/highlighters/brackets/brackets-highlighter.zsh
fresh zsh/zsh-syntax-highlighting.zsh

fresh will resolve local files (fresh zsh/zsh-syntax-highlighting.zsh) based on where the freshrc is sourced from.

The .freshrc extention would be optional.

🤘

If you have a fresh line with a glob:

fresh 'config/*' --file

With the following directory structure:

config/ackrc
config/pryrc
config/foo/bar

We get the following error:

cat: /Users/foo/.dotfiles/config/foo: Is a directory

We should also test this when using --ref.

Test: it_should_not_recurse_into_subdirectories.

Would be handy to lock an entry to a specific git ref.

To DRY up the following pattern in the tests:

  # ...
  bin/fresh clean > "$SANDBOX_PATH/out.log" 2> "$SANDBOX_PATH/err.log"
  assertTrue 'successfully cleans' $?

  assertFileMatches $SANDBOX_PATH/out.log <<EOF
Removing ~/.dead
Removing ~/bin/dead
EOF
  assertFileMatches $SANDBOX_PATH/err.log <<EOF
EOF
  # ...

Allow:

fresh vim/colors/bclear_custom.vim      --file=~/.vim/colors/bclear_custom.vim
fresh vim/colors/jellybeans_custom.vim  --file=~/.vim/colors/jellybeans_custom.vim
fresh vim/colors/solarized_custom.vim   --file=~/.vim/colors/solarized_custom.vim

To be:

fresh 'vim/colors/*'   --file=~/.vim/colors/

freshrc:

fresh zsh-users/zsh-syntax-highlighting zsh-syntax-highlighting.zsh --file=vendor/zsh-syntax-highlighting.zsh
fresh zsh-users/zsh-syntax-highlighting highlighters/brackets/brackets-highlighter.zsh --file=vendor/highlighters/brackets/brackets-highlighter.zsh

Copies brackets-highlighter.zsh from zsh-users/zsh-syntax-highlighting into ~/.fresh/build/vendor/highlighters/brackets/brackets-highlighter.zsh.

zshrc:

source "$FRESH_BUILD_PATH/vendor/zsh-syntax-highlighting.zsh"

$FRESH_PATH/build/bin/fresh not existing after building probably means the user accidentally omitted Fresh from their freshrc file. We should probably warn them about this and possibly provide resolution instructions.

Ideally we should check during build before we move build.new into place. This will prevent the user ending up in an state where fresh is unavailable.