Keybase proof
I hereby claim:
- I am floer32 on github.
- I am floer32 (https://keybase.io/floer32) on keybase.
- I have a public key ASCFzHi3EEAaSJy8GuhO3RSNh3tEz8iQ9KTkpJr3yiE5xgo
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
main
git ribbon
, git catchup
I've used these for years (found here)
git ribbon
to mark latest main you've reviewed (like a ribbon in a journal)git catchup
to review diff since then. (then do git ribbon
again after reviewing, so it's ready for tomorrow.)In your ~/.gitconfig
, [aliases]
section:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --auto-open-devtools-for-tabs
Canary:
/Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary --auto-open-devtools-for-tabs
ℹ️ There's also an Alfred Workflow for searching and grabbing this directory.
Directory with all Alfred Workflows:
cd /Applications/AlfredSync/Alfred.alfredpreferences/workflows
What's a Uniform Type Identifier?
Each UTI provides a unique identifier for a particular file type, data type, directory or bundle type, and so on. In addition, other type identifier namespaces for a particular type can be grouped under one UTI, with utility functions available to translate from one format to another.
The following tables list uniform type identifiers (UTIs) that are declared by the system as of OS X v10.4. [Which was released in 2005. That means it's NOT up to date. Apple Developer stuff has the up to date docs. Still, these can be useful for scripting, Alfred Workflows, and so on.]
Note: T
problem:
Error configuring SDK: [...].
Please make sure that [... ruby path, from asdf or otherwise ...] is a valid home path for this SDK type.
solution that worked for me:
- close RubyMine
" copy all this into a vim buffer, save it, then... | |
" source the file by typing :so % | |
" Now the vim buffer acts like a specialized application for mastering vim | |
" There are two queues, Study and Known. Depending how confident you feel | |
" about the item you are currently learning, you can move it down several | |
" positions, all the way to the end of the Study queue, or to the Known | |
" queue. | |
" type ,, (that's comma comma) |
export HERE="$( cd "$(dirname "$0")" >/dev/null 2>&1 ; pwd -P )" | |
# example usage - source a script in same directory. but using absolute path, | |
# ... which you'd do so that a script can be called from wherever. (not dependent on working directory ($PWD)) | |
. "${HERE}/common.sh" | |
# ... or of course you could export DIRNAME or whatever you want. | |
# In scripts I just find "$HERE/node_modules", "$HERE/src" etc to be pretty readable. |
When life gives you lemons, make hummus |