Runs Previous Command with Replace
For some reason most of my typos happen within iTerm, which is kind of funny when you consider most commands are super short. gut push doesn't do what I want, nor does hg ammend or any other command spelled wrong. Then you have to either retype the whole thing or press the up key, place the cursor in the right spot, then update the bad text. Blah.
I recently learned a cool trick for executing the previous command but with a text replacement shortcut:
# `gut push` -- Oooops!
^gut^git # Replaces "gut" with "git" and executes previous command!
# `hg ammend` -- Oooops!
^ammend^amend
No need to retype and no need to fix the text within the entire command. Neat way to save time and get things done!
![Page Visibility API]()
One event that's always been lacking within the document is a signal for when the user is looking at a given tab, or another tab. When does the user switch off our site to look at something else? When do they come back?
![CSS @supports]()
Feature detection via JavaScript is a client side best practice and for all the right reasons, but unfortunately that same functionality hasn't been available within CSS. What we end up doing is repeating the same properties multiple times with each browser prefix. Yuck. Another thing we...
![Introducing MooTools Dotter]()
It's best practice to provide an indicator of some sort when performing an AJAX request or processing that takes place in the background. Since the dawn of AJAX, we've been using colorful spinners and imagery as indicators. While I enjoy those images, I am...
![Redacted Font]()
Back when I created client websites, one of the many things that frustrated me was the initial design handoff. It would always go like this:
Work hard to incorporate client's ideas, dream up awesome design.
Create said design, using Lorem Ipsum text
Send initial design concept to the client...
Really cool trick, David! Hadn’t come across this one yet. I’m the curious type so I just had to know what this is called, and any other details… It looks like after a little research that this is a Bash feature, and it’s called “quick substitution”. Its documented under the “Event Designators” section of Bash documentation:
http://www.gnu.org/software/bash/manual/bashref.html#Event-Designators
The documentation specifies the usage as:
But I just tried it out myself and it looks like it works just fine without the trailing caret character. By the way, it’s probably worth noting that this will only replace the first instance of “string1” in the command, so if you misspelled something twice in the command (seems unlikely, I know) you would have to use:
This works with Zsh too.
Thanks Rose Hosting, good catch!
http://zsh.sourceforge.net/Doc/Release/Expansion.html#Overview
If you use zsh, you can enable auto-correction, so if you type
then it will say
This is a great tip.
P.S. Lately, most of my php/css/js related google searches have been showing your site near the top. I have picked up a lot of new things from your site. Whatever you are doing with SEO and content, it is amazing.
All the best.
PPS. I hope one day your have email newsletters.