4 ms·
Using WIP branches to save every edit
- MartinMond 17y agoIt's a really useful time save. Unfortunaly git-wip by default doesn't commit files that are untracked (e.g. new). I submitted a patch to do exactly this: http://github.com/MSch/git-wip/commit/22f4b57b67762a0123d1ba319e82a0bc2a4ce338 http://github.com/MSch/git-wip/commit/22f4b57b67762a0123d1ba...
- windsurfer 17y agoWhy not have a daemon track for file state changes instead of having every editor run the git wip command? That would be much more general and probably better for most projects. Maybe I'll make such a daemon...
- RiderOfGiraffes 17y agoDoesn't "tripwire" allow something like that? I'm not personally familiar with it and don't use it, but I'm sure I've seen something about it.
- weaksauce 17y agoFrom my understanding of it that is how dropbox operates. Updating after every file save by hooking into the file system somehow.
- alxv 17y agoA custom daemon would be great, but meanwhile you could use inotify-tools from the shell: while inotifywait -r -e modify . do git wip save "automatic save" done
- jed_s 17y agothis should be integrated into editors as undo/redo i've long thought proper version control makes sense if it's fast enough -- eventually everything will be tracked anyway. it doesn't make any sense to lose any ideas just because only one of them was "the winner".
- skorgu 17y agoThis is timely considering just last night I "rm -rf projectname.py" instead of "rm -rf projectname.sqlite". D'oh.
- akkartik 17y agoHow does this compare with git stash?
- ivey 17y agoAnyone have it working in Emacs? I may fool around with it tonight, if not, and see if I can get it working.
- cschneid 17y agoI'm a vim guy myself, but looks like you just need the onSave hook that the vi config at the end calls.