Guards pretty cool but in my experience it's far too easy to outpace, especially if you're loading rails in all of your specs.
I abandoned it pretty quickly in favour of a couple of quick vim keybindings just beacuse I'd be editing a test and then switch to terminal and have to wait for 2 maybe 3 cycles for Guard to catch up with the current state of my specs. just my 2 cents though. M On Fri, Feb 17, 2012 at 12:31 PM, Tekin Suleyman <[email protected]> wrote: > Further to yesterdays talk (thanks again Ash), I came across a nice trick > using the guard gem: automatic browser refreshing on code changes: > > http://railscasts.com/episodes/264-guard?view=asciicast > > Sexy! > > -- > Tekin Suleyman > -- > http://tekin.co.uk > Twitter http://twitter.com/tekin > > -- > You received this message because you are subscribed to the Google Groups > "NWRUG" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/nwrug-members?hl=en. > -- Matt House http://eightbitraptor.com @eightbitraptor -- You received this message because you are subscribed to the Google Groups "NWRUG" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nwrug-members?hl=en.
