Tested in Mac OS X: super == command
Open/Goto
- super+t: go to file
- super+ctrl+p: go to project
- super+r: go to methods
00 01 * * * /bin/bash --login -c 'cd <your app> && RAILS_ENV=production /usr/bin/env bundle exec rake <your rake>' >> /var/log/<your app>.log 2>&1 |
# Asserting a link based on HREF | |
Then /^(?:|I )should see a link to (.+?)(?: with the text "([^\"]*)")?(?: within "([^\"]*)")?$/ do |page_name, text, selector| | |
with_scope(selector) do | |
page.should have_css("a[href='#{ path_to(page_name) }']", :text => text) | |
end | |
end | |
Then /^(?:|I )should see a mailto link for "([^\"]*)"(?: with the text "([^\"]*)")?(?: within "([^\"]*)")?$/ do |email_address, text, selector| | |
with_scope(selector) do |
Hello, visitors! If you want an updated version of this styleguide in repo form with tons of real-life examples… check out Trellisheets! https://github.com/trello/trellisheets
“I perfectly understand our CSS. I never have any issues with cascading rules. I never have to use !important
or inline styles. Even though somebody else wrote this bit of CSS, I know exactly how it works and how to extend it. Fixes are easy! I have a hard time breaking our CSS. I know exactly where to put new CSS. We use all of our CSS and it’s pretty small overall. When I delete a template, I know the exact corresponding CSS file and I can delete it all at once. Nothing gets left behind.”
You often hear updog saying stuff like this. Who’s updog? Not much, who is up with you?