idleberg

File type	Sublime Text	Atom
ActionScript	source.actionscript.2	?
AppleScript	source.applescript	[.source.applescript]
ASP	source.asp	?
Batch File	source.dosbatch	?
BibTex	source.bibtex	?
BridleNSIS	[source.nsis.bridle]	[.source.nsis.bridle]
C	source.c	[.source.c]
C#	source.cs	[.source.cs]

idleberg

#!/bin/sh

# For installation and usage, please refer to my blog post:
# http://derekstavis.github.io/posts/creating-a-installer-using-inno-setup-on-linux-and-mac-os-x/
#
# The MIT License (MIT)
#
# Copyright (c) 2014 Derek Willian Stavis
#
# Permission is hereby granted, free of charge, to any person obtaining a copy

idleberg

This list has been updated for Big Sur (and later). Since I don't use these versions, this guide might still need further improvements. For older macOS versions, please see this older revision.

Open in Sublime Text

• Open Automator
• Quick Action
• Set “Service receives selected” to files or folders in any application
• Add a Run Shell Script action
• Set the script action to /Applications/Sublime\ Text.app/Contents/SharedSupport/bin/subl -n "$@"
• Set “Pass input” to as arguments

idleberg

Auto-deploying built products to gh-pages with Travis

This is a set up for projects which want to check in only their source files, but have their gh-pages branch automatically updated with some compiled output every time they push.

Create a compile script

You want a script that does a local compile to e.g. an out/ directory. Let's call this compile.sh for our purposes, but for your project it might be npm build or gulp make-docs or anything similar.

The out/ directory should contain everything you want deployed to gh-pages. That almost always includes an index.html.

idleberg

<?php

/**
 * Case-insensitive in_array() wrapper.
 *
 * @param  mixed $needle   Value to seek.
 * @param  array $haystack Array to seek in.
 *
 * @return bool
 */