Neither is fork or pull request something that you can't do easily without Bitbucket and Github, but people still use them mainly because those two sites make it easier for them to fork a project and keep the fork up to date. I guess it's all about convenience, and time will tell if people will use it.
This looks good. For cpu and memory checks I find htop to be more lightweight and functionality wise is pretty good too.
It doesn't show disk stats though, for which something like atop should be used.
It depends upon the hardware you have. But if you have a decent machine say EC2 small instances or something like http://www.hetzner.de/en/hosting/produkte_vserver/vq19 it should not be an issue. We use similar setup for promptcloud and that machine has numerous other things running too, there is no noticeable load.
>I'm a bit stumped on toggling comments, though. Any ideas?
" comentify/uncommentify a line or a visual block"
function! Komment()
if getline(".") =~ '^[ \t]*#'
let hls=@/
s/^\([ \t]*\)#\(.*\)$/\1\2
let @/=hls
else
let hls=@/
s/^\([ \t]*\)\(.*\)$/\1#\2
let @/=hls
endif
endfunction
:vnoremap // :call Komment()<CR>
:nnoremap // :call Komment()<CR>
If you want to use c style comment :
function! Komment()
if getline(".") =~ '^[ \t]*\/\*'
let hls=@/
s/^\(\s*\)\/\*\(.*\)\*\/\(\s*\)$/\1\2\3/
let @/=hls
else
let hls=@/
s/[ \t]*$//
s/^\(\s*\)\(.*\)\(\s*\)$/\1\/\* \2 \*\//
let @/=hls
endif
endfunction
:vnoremap <silent> // :call Komment()<CR>
:nnoremap <silent> // :call Komment()<CR>
Darcs is good for personal use, but I moved away primarily because of the exponential merge problem. I think darcs2 takes care of it in most of the cases but NOT always. That is a big question mark for production repository. Darcs is easy to get started with though - to anybody interested I recommend this link - http://blog.interlinked.org/tutorials/darcs.html .
http://www.ghacks.net/2013/03/14/the-ultimate-google-reader-...
http://reviews.cnet.com/8301-19512_7-57574201-233/google-rea...