-
remotesplit for cscope revisited
I’ve decided to go with a remote tactic that’s slightly more reliable than my previous tactic: Name the gvim server by the contents of the $DISPLAY variable. I have side-by-side PCs with their own X-servers, so I want to send the file to the gvim server that is outputting the same place as my cscope […]
-
More than Enough.
After making it through More Than Enough, I finally understand the structure. If you do read this book, don’t cheat yourself by skipping the cumulative review sessions at the end of each chapter. They help reinforce a mindset that is a key to getting your priorities in order.
-
remotesplit for cscope
On a multiuser environment, I added the ‘ps -fu’ bit to detect a gvim session, slightly more fool-resistant than just checking the result code of the –remote-send call. My remotesplit: ps -fu $LOGNAME | grep -v grep | grep gvim 2>/dev/nullif [ $? -ne 0 ]then gvim $*else gvim –remote-send “<ESC>:sp $CSCOPE_ROOT/$2<CR>:0<CR>:$1<CR>:-1<CR>” 2>/dev/nullfi