Want to create a Gist from your editor, the command line, or the Services menu? Here's how.
http://hea-www.harvard.edu/~fine/OSX/unicode_apple_logo.html
- -

-
- the Apple Symbol - ⌘ -
⌘
-⌘
- the Command Key symbol - ⌥ -
⌥
-⌥
- the Option Key symbol - ⇧ -
⇧
-⇧
- the Shift Key symbol - ⎋ -
⎋
-⎋
- the Escape Key symbol
And while we're at it, some related (not mac-specific):
-- from http://www.tuaw.com/2011/03/14/use-applescript-to-open-current-safari-url-in-google-chrome/ | |
-- install FastScripts http://www.red-sweater.com/fastscripts/ and place this AppleScript in the Scripts applications folder for Google Chrome. | |
-- For me that was ~/Library/Scripts/Applications/Safari | |
-- You can then assign it a keyboard shortcut. I went with Cmd-Shift-C | |
property theURL : "" | |
tell application "Safari" | |
set theURL to URL of current tab of window 1 | |
end tell | |
tell application "Google Chrome" |
// ==UserScript== | |
// @name Use Markdown, sometimes, in your HTML. | |
// @author Paul Irish <http://paulirish.com/> | |
// @link http://git.io/data-markdown | |
// @match * | |
// ==/UserScript== | |
// If you're not using this as a userscript just delete from this line up. It's cool, homey. |
#301 Redirects for .htaccess | |
#Redirect a single page: | |
Redirect 301 /pagename.php http://www.domain.com/pagename.html | |
#Redirect an entire site: | |
Redirect 301 / http://www.domain.com/ | |
#Redirect an entire site to a sub folder | |
Redirect 301 / http://www.domain.com/subfolder/ |
/* WITH MODS TO ORIG -- iOS Browser Bookmarklets to launch other apps and stuff */ | |
/* ver 2014-04-14a */ | |
/* backing up my "Open In" bookmarks */ | |
// note iOS6 requires some changes to these | |
// BEGIN TESTING STUFF -- IN PROFRESS LIKELY NOT WORKING | |
// SOME WORK, MOST tests are not WORK -- | |
// PINNER APP TEST STUFF (as a private one) | |
// the page title as the title and your selected text as the description. |
#!/bin/sh | |
### | |
# SOME COMMANDS WILL NOT WORK ON macOS (Sierra or newer) | |
# For Sierra or newer, see https://github.com/mathiasbynens/dotfiles/blob/master/.macos | |
### | |
# Alot of these configs have been taken from the various places | |
# on the web, most from here | |
# https://github.com/mathiasbynens/dotfiles/blob/5b3c8418ed42d93af2e647dc9d122f25cc034871/.osx |
/usr/bin/plutil -convert xml1 -o - ~/Library/Safari/Bookmarks.plist | grep -E -o '<string>http[s]{0,1}://.*</string>' | grep -v icloud | sed -E 's/<\/{0,1}string>//g' |
/** | |
* Get YouTube ID from various YouTube URL | |
* @author: takien | |
* @url: http://takien.com | |
* For PHP YouTube parser, go here http://takien.com/864 | |
*/ | |
function YouTubeGetID(url){ | |
var ID = ''; | |
url = url.replace(/(>|<)/gi,'').split(/(vi\/|v=|\/v\/|youtu\.be\/|\/embed\/)/); |
#Introduction
Developing Chrome Extensions is REALLY fun if you are a Front End engineer. If you, however, struggle with visualizing the architecture of an application, then developing a Chrome Extension is going to bite your butt multiple times due the amount of excessive components the extension works with. Here are some pointers in how to start, what problems I encounter and how to avoid them.
Note: I'm not covering chrome package apps, which although similar, work in a different way. I also won't cover the page options api neither the new brand event pages. What I explain covers most basic chrome applications and should be enough to get you started.