--
You received this message because you are subscribed to the Google Groups "Singapore Ruby Brigade" group.
To post to this group, send email to singap...@googlegroups.com.
To unsubscribe from this group, send email to singapore-rb...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/singapore-rb?hl=en.
Sent via BlackBerry from SingTel!
--
You received this message because you are subscribed to the Google Groups "Singapore Ruby Brigade" group.
To post to this group, send email to singap...@googlegroups.com.
To unsubscribe from this group, send email to singapore-rb...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/singapore-rb?hl=en.
On a similar vein, has anybody used git to vc his/her ~/ ?
--
You received this message because you are subscribed to the Google Groups "Singapore Ruby Brigade" group.
To post to this group, send email to singap...@googlegroups.com.
To unsubscribe from this group, send email to singapore-rb...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/singapore-rb?hl=en.
By moving deleted files into a folder in the same path, we avoid massive copy for deleting large files.
I subversion'd my homedir a couple years ago, then migrated to git.
http://haller.ws/logs/view.cgi/SubversionHomeDir/
The biggest gain is non-intuitive. Normally, we treat config files as
detritus, and when we move to a new machine, we reconfig ourselves to
match the new setup.
By putting dotfiles in a repo, our developer brains immediately view
them as maintained files. We then improve them, and this helps us learn
our tools as we customize them to fit how we work.
You end up with a better machine-human interface in addition to the file
distribution / backup / versioning that comes with a VCS.
Patrick
rm() {
local secs=$( system.time.epoch )
local archive="${RM_ARCHIVE}/${secs}"
[[ ! -d ${archive} ]] && mkdir -p "${archive}"
[[ ! -d ${archive} ]] && { echo "rm: unable to mkdir ${archive}" ; return 1; }
for i in "$@"; do
[[ -S "$i" ]] && command rm "$i"
[[ -e "$i" ]] && command mv "$i" ${archive}/.
done
}
in the same filesystem, perhaps. it'd be nice for rmdir to be able to work. why not maintain a shadow filesystem under /.Trash/, effectively journaling as you go? instead of copy-on-write, it'd be mv-on-rm.
rm() {
local secs=$( system.time.epoch )
local archive="${RM_ARCHIVE}/${secs}"
[[ ! -d ${archive} ]] && mkdir -p "${archive}"
[[ ! -d ${archive} ]] && { echo "rm: unable to mkdir ${archive}" ; return 1; }
for i in "$@"; do
[[ -S "$i" ]] && command rm "$i"
[[ -e "$i" ]] && command mv "$i" ${archive}/.
done
}
then background the mv in the function ;)
then background the mv in the function ;)
--
I just find that a 2sec pause before a rm and a Crashplan subscription save me from all that trouble :)
I just find that a 2sec pause before a rm and a Crashplan subscription save me from all that trouble :)That's not a bad idea. A few seconds pause does save me from sending an email to a wrong person :)
--
maybe you can implement the same functionality as gmail goggles.if you want to delete a fileyou need to answer a series of arithmetic questions.
override rm ;)rm() {
local secs=$( system.time.epoch )
local archive="${RM_ARCHIVE}/${secs}"
[[ ! -d ${archive} ]] && mkdir -p "${archive}"
[[ ! -d ${archive} ]] && { echo "rm: unable to mkdir ${archive}" ; return 1; }
for i in "$@"; do
[[ -S "$i" ]] && command rm "$i"
[[ -e "$i" ]] && command mv "$i" ${archive}/.
done
}
Hooray!
patrick,
if u remember we put the magic-space into my inputrc.
but unconditionally!
as a result, i couldn't type space in my mongodb shell,
for 2 months! :)
now, i saw in ur inputrc, what is the way to go about it:
$if Bash
Space: magic-space
...
so, thx!
ivan,
im completely agree that ppl today should still look back at
engelbart's work!
while im saying that, i've just realized that even myself haven't
watched the full demo yet... just half of it... :)
sharing a more direct link to the videos might raise the chance
of ppl actually watching it, i think:
http://sloan.stanford.edu/MouseSite/1968Demo.html
roland,
where can we see your ssh_config?
martin,
thx for pointing out fish.
just read the wikipedia page, but i was happy to see there are
efforts to clean up the shortcomings of sh.
jason, keep on going.
u r great at organizing communities!
--
tom