This is a fork of and builds upon the work of Eddie Webb's search and Matthew Daly's search explorations.
It's built for the Hugo static site generator, but could be adopted to function with any json index.
To see it in action, go to craigmod.com and press CMD-/ and start typing.
Custom recipe to get OS X 10.11 El Capitan running from scratch, setup applications and developer environment. This is very similar (and currently mostly the same) as my 10.10 Yosemite setup recipe (as found on this gist https://gist.github.com/kevinelliott/0726211d17020a6abc1f). Note that I expect this to change significantly as I install El Capitan several times.
I use this gist to keep track of the important software and steps required to have a functioning system after a semi-annual fresh install. On average, I reinstall each computer from scratch every 6 months, and I do not perform upgrades between distros.
This keeps the system performing at top speeds, clean of trojans, spyware, and ensures that I maintain good organizational practices for my content and backups. I highly recommend this.
You are encouraged to fork this and modify it to your heart's content to match your own needs.
To fix:
sudo ln -s /System/Library/Frameworks/Ruby.framework/Versions/2.0 /System/Library/Frameworks/Ruby.framework/Versions/1.8
This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.
I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.
Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.
| #!/bin/bash | |
| # | |
| # crashplanFixup.sh for Macintosh OS X 10.9 (and probably earlier versions) | |
| # | |
| # This script will prevent CrashPlan from de-duplicating data on files greater than 1k. | |
| # Based on information from http://networkrockstar.ca/2013/09/speeding-up-crashplan-backups/ | |
| # | |
| # NOTE: Must be run with sudo! IE: $ sudo sh ./crashplanFixup | |
| # | |
| # v1.1 2014-03-13 by bill@wellingtonnet.net |
| #!/usr/bin/ruby | |
| # SIFTTTER 1.5: An IFTTT-to-Day One Logger by Craig Eley 2014 <http://craigeley.com> | |
| # Based on tp-dailylog.rb by Brett Terpstra 2012 <http://brettterpstra.com> | |
| # Multiple Date Function by Paul Hayes 2014 <http://paulrhayes.com> | |
| # | |
| # Notes: | |
| # * Uses `mdfind` to locate a specific folder of IFTTT-generated text files changed in the last day | |
| # * The location of your folder should be hardcoded in line 67, and the location of your Day One in line 66 | |
| # * Scans leading timestamps in each line matching the selected dates | |
| # * Does not alter text files in any way |
| (* EXPORT ALL SKIM NOTES TO EVERNOTE WITH HYPERLINKS | |
| -- Stephen Margheim | |
| -- 9/7/13 | |
| -- open source | |
| REQUIRED PROGRAMS: | |
| - Skim (pdf viewer and annotator) | |
| - Evernote (cloud based note app) |
I wanted to outline a potential system for organizing Sass declarations. Since Alphabetization has also been a hot topic (of which I am in favor), it outlines how things such as nesting, @extend, @include, and comments would all fall into the same system. This is by no means a perfect system - but after using Sass for a variety of different things, this is the organization I've found that can deal most easily with edge cases.
Please feel free to critique / edit / etc.
| /* This stylesheet is designed to work with the grey theme for GMail | |
| - hides the top bar and Google+ notifications | |
| - simplifies buttons (remove border/background, add hover state back) | |
| - dim Rapportive until hovered | |
| This is only partially tested at this point and may cause some issues | |
| Please let me know if you find problems: <http://brettterpstra.com/contact/> | |
| Brett Terpstra 2013 <http://brettterpstra.com> /* |