{"id":2214,"date":"2016-04-11T10:00:09","date_gmt":"2016-04-11T15:00:09","guid":{"rendered":"https:\/\/www.foell.org\/justin\/?p=2214"},"modified":"2019-10-21T11:51:12","modified_gmt":"2019-10-21T16:51:12","slug":"emacs-on-osx","status":"publish","type":"post","link":"https:\/\/www.foell.org\/justin\/emacs-on-osx\/","title":{"rendered":"Emacs on OSX"},"content":{"rendered":"

So, I started a new job. Besides actually leaving my home to at least occasionally go into the office<\/a>, the other big change is I’ve been given a brand-spanking-new MacBook Pro to use (our shop is a part of the Apple Consultant Network<\/a>).<\/p>\n

While using Linux professionally for the last 13 years is sort of coming to an end, Linux certainly isn’t going away from my life, especially after using it almost exclusively at home for 20 years.<\/p>\n

The MacBook is still a BSD unix system at heart – with some great hardware, and a lovely, albeit sometimes frustrating, user interface laid on top. Mac enthusiasts might abhor that the only application I set to launch on boot is the terminal. This article is not for them, because in old-school fashion I’m going to cover installing and using Emacs and some other extras in OSX.<\/p>\n

<\/p>\n

Installing Emacs<\/h2>\n

Installing Emacs via homebrew<\/a> is very easy so I won’t go into it, you can follow these instructions: http:\/\/wikemacs.org\/wiki\/Installing_Emacs_on_OS_X#Homebrew<\/a><\/p>\n

OSX 10.11 (El Capitan) actually includes GNU Emacs 22, but it’s only the terminal based version. If you want the newest version and a full GUI, follow the homebrew instructions above. If you need to move or rename the old version, you may need to keep OSX’s attributes and latest security layers in mind<\/a>. Rather than moving my old version, I added an alias to my ~\/.bashrc<\/code>:<\/p>\n

alias emacs=\"\/usr\/local\/Cellar\/emacs\/24.5\/Emacs.app\/Contents\/MacOS\/Emacs\"<\/pre>\n
However, OSX’s bash won’t read and run~\/.bashrc<\/code><\/a>, only ~\/.bash_profile<\/code>, so to my ~\/.bash_profile<\/code> I added:<\/p>\n
[[ -s ~\/.bashrc ]] && source ~\/.bashrc<\/pre>\n
In my ~\/.bash_profile<\/code> I also added a ~\/bin<\/code> directory to my path where I can put custom scripts:<\/p>\n
export PATH=\"~\/bin:$PATH\"<\/pre>\n
To shorten up emacs<\/code> I added a shell script called em<\/code> to my ~\/bin<\/code> directory:<\/p>\n
#!\/bin\/sh\r\nopen -n -a \/Applications\/Emacs.app \"$@\" &\r\n<\/pre>\n
One caution about doing something similar to this is that em<\/code> (edit) is now very<\/em> close to rm<\/code> (remove) since the ‘E’ and ‘R’ keys are neighbors. Just make sure you know what you’ve typed before hitting return \ud83d\ude42<\/p>\n
Fix Home\/End Keys<\/h2>\n
I’m not sure why the Home\/End keys don’t have normal behavior as I’ve become accustomed to. Here are some fixes I’ve found that work:<\/p>\n
Home\/End for most applications<\/a><\/h3>\n
$ mkdir -p ~\/Library\/KeyBindings\/<\/pre>\n
$ vi ~\/Library\/KeyBindings\/DefaultKeyBinding.dict<\/pre>\n
Then add the following:<\/p>\n
{\r\n    \"\\UF729\"  = moveToBeginningOfParagraph:; \/\/ home\r\n    \"\\UF72B\"  = moveToEndOfParagraph:; \/\/ end\r\n    \"$\\UF729\" = moveToBeginningOfParagraphAndModifySelection:; \/\/ shift-home\r\n    \"$\\UF72B\" = moveToEndOfParagraphAndModifySelection:; \/\/ shift-end\r\n}\r\n<\/pre>\n
Home\/End in Terminal<\/h3>\n
Open Terminal, then go to Terminal -> Preferences…<\/p>\n
Go to the Profiles section, highlight the terminal profile you use the most, then click the “Keyboard” tab. You’ll probably have to add two new entries for Home and End, but first highlight F1, click edit, then copy the \\033OP action code so you can paste it in the new codes. Click cancel after copying the F1 code.<\/p>\n
Click ‘+’ to add Home. Choose Key: “Home”, Modifier: “None”, Action: “Send Text:”, and paste in the action code. Click “Delete One Character” and then type “H”. You should end up with \\033OH for Home. Follow the same procedure for End, but map it to \\033OF.<\/p>\n
Home\/End In Emacs<\/h3>\n
Edit your ~\/.emacs<\/code> file (you could instead edit it with Emacs and it would be oh so meta).<\/p>\n
$ vi ~\/.emacs<\/pre>\n
Add the following:<\/p>\n
; Fix home\/end in OSX\r\n(define-key global-map [home] 'beginning-of-line)\r\n(define-key global-map [end] 'end-of-line)<\/pre>\n
PHP Add-ons<\/h3>\n
I wanted to add a PHP Code Sniffer to do syntax checking and documentation\/standards enforcement. To add it via homebrew, I first needed to add the alternate homebrew-php repository. See the installation instructions here<\/a>. Then I could install phpcs:<\/p>\n
brew install php-code-sniffer<\/pre>\n
I added this because I want to use the official PHP Code Sniffer for WordPress<\/a>.<\/p>\n
I installed the Code Sniffer for WordPress from github into my ~\/Sites<\/code> directory and then added it to my phpcs configuration by running:<\/p>\n
phpcs --config-set installed_paths \/Users\/jfoell\/Sites\/WordPress-Coding-Standards<\/pre>\n
Then I verified that it was installed by running:<\/p>\n
phpcs -i<\/pre>\n
The installed coding standards are MySource, PEAR, PHPCS, PSR1, PSR2, Squiz, Zend, WordPress, WordPress-Core, WordPress-Docs, WordPress-Extra and WordPress-VIP<\/p>\n
PHP Code Sniffer in Emacs via MELPA and Flycheck<\/h3>\n
I added MELPA stable packages<\/a> to my ~\/.emacs<\/code> file (see their installation instructions), then updated MELPA from within Emacs:<\/p>\n
M-x package-list-packages RET<\/pre>\n
Then I installed the flycheck extension (which will use PHP CodeSniffer to do on-the-fly syntax checking):<\/p>\n
M-x package-install RET flycheck RET<\/pre>\n
Then I added the following default phpcs standard setting and init hook to my ~\/.emacs<\/code> file:<\/p>\n
(custom-set-variables\r\n '(flycheck-phpcs-standard \"WordPress\")\r\n)\r\n\r\n(add-hook 'after-init-hook #'global-flycheck-mode)<\/pre>\n
Other Emacs and Terminal Goodies<\/h2>\n
To add Tab Bar Mode<\/a> support, I cloned the Aquamacs tabbar project<\/a> into ~\/.elisp\/tabbar<\/code>. Then I added these lines to my ~\/.emacs<\/code> file to load the tabbar library and start tab bar mode automatically:<\/p>\n
\r\n;; Load custom tabbar mode\r\n(load-file \"~\/.elisp\/tabbar\/tabbar.el\")\r\n(tabbar-mode)\r\n<\/pre>\n
Lastly, here’s a great article on getting the terminal prompt and output to look a little nicer: http:\/\/osxdaily.com\/2013\/02\/05\/improve-terminal-appearance-mac-os-x\/<\/a><\/p>\n
Happy Hacking!<\/p>\n
Send to Kindle<\/span><\/div>","protected":false},"excerpt":{"rendered":"
So, I started a new job. Besides actually leaving my home to at least occasionally go into the office, the other big change is I’ve been given a brand-spanking-new MacBook Pro to use (our shop is a part of the Apple Consultant Network). While using Linux professionally for the last 13 years is sort of… Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"Emacs on OSX - retrogrouchery at it's finest","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[1,8,22],"tags":[116,12,166,152,151],"class_list":["post-2214","post","type-post","status-publish","format-standard","hentry","category-business","category-ubuntu","category-wordpress","tag-apple","tag-emacs","tag-linux","tag-mac","tag-osx"],"aioseo_notices":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.foell.org\/justin\/wp-json\/wp\/v2\/posts\/2214","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.foell.org\/justin\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.foell.org\/justin\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.foell.org\/justin\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.foell.org\/justin\/wp-json\/wp\/v2\/comments?post=2214"}],"version-history":[{"count":12,"href":"https:\/\/www.foell.org\/justin\/wp-json\/wp\/v2\/posts\/2214\/revisions"}],"predecessor-version":[{"id":3580,"href":"https:\/\/www.foell.org\/justin\/wp-json\/wp\/v2\/posts\/2214\/revisions\/3580"}],"wp:attachment":[{"href":"https:\/\/www.foell.org\/justin\/wp-json\/wp\/v2\/media?parent=2214"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.foell.org\/justin\/wp-json\/wp\/v2\/categories?post=2214"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.foell.org\/justin\/wp-json\/wp\/v2\/tags?post=2214"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}