Attention users of gvim on OS X:
your workspace saving dreams have become reality.
Let's take a scenario:
You are a programmer named Brucey. Hi Brucey. Often times, in the evenings once you are one with the various duties thrust upon you by the giant corporation you call daddy, you like to relax by writing implementations of computer languages created by people with last names that start with a 'K' in Python.
When you wake up in the morning late for work with your laptop burning a hole through your blankets where you left it when you passed out while holding down the return key, you realize you need to get to work fast but you don't want to lose the 16
gvimwindows you've got open working on your code. Unfortunately, you are stuck in the pre-wsdark ages and have no easy way to do this so you call in to work sick out of depression and lose your job. Sucks to be you, Brucey.
Don't let this happen to you. Meet ws, a quick hack of a script to find all your gvim instances, their current working directories, and the files they have open, save them and load them later. It is simple alright, but oh so delicious.Here's how you might have ended that scenario different with ws:
The terminal you were holding down enter in happens to be at the root of your project directory,
~/p/plog, so you casually typews saveat your tricked-outzshprompt and a .saved_workspace file is written to your current directory.You then close all your windows and get to work just in time to find out the boss is out sick meaning you are free to keep working on your wicked-ass code, so you pop back to your project directory,
~/p/plog, and drop the bombs withws load. Hoorah, gvim windows. You finish your implementation, suddenly realize it solves world hunger and moments later are awarded the Nobel Prize for Excellency in Bad-ass-ness. Good job, Brucey.
Remember kids, this could all be yours if use ws!
Now here's a picture a sea lion passed out after it won the nobel bad-ass-ness prize for using ws:
Technorati Tags: code