aljachimiak/fur

An experiment: recreating git with bash and ruby.

fur's Issues

Future Feature - Error handling

Only two commands can run outside of a fur directory without a ruby error:

$ fur
$ fur help

Any other command will throw a ruby error because .fur/ doesn't exist at the level of the run command.

Feature - Elegant Errors

Running any of these commands:

$ fur store
$ fur restore
$ fur forward
$ fur back

Should:
1 check for .fur directory
2 if no .fur directory return "This is not a fur project directory. Run fur init to start a fur project here."
3 if there is a .fur directory, carry on...

Special consideration:

$ fur status

Perhaps a different error message?

Future Feature - Erasing your future

Consider the following premise:

1. You have run fur init on a project
2. You have run fur store five times and your fur pointer is at 6
3. You run fur back three times to view an old version; your fur pointer is at 3
4. You make changes and decide to go in a new direction
5. You run fur store to save your changes; your fur pointer is a 4

This is where the problem lies
You have two more diffs in .fur/diffs/ called 4.f and 5.f that refer back to potentially non-existant lines, directories, or files.

Feature - Erase the future

At #5 in the situation above, fur store should do the following:

1. check to see if #{pointer}.f exists
2. prompt user: "You are about to destroy #{ #{number of .fur/diffs/} - 1 } future versions. Do you want to store your project and continue? [y/n]
3. if [y], continue with store; and:
   3.5. loop through the .fur/diffs directory and rm all i.f files that are greater than the #{new fur pointer}.
4. if [n]; Return a message: "Your changes have not been stored"