adoublef

type Booleanish = boolean | "true" | "false";
type CrossOrigin = "anonymous" | "use-credentials" | "" | undefined;

// export = JSX;
// export as namespace JSX;

declare namespace JSX {
    interface HTMLProps<T> extends AllHTMLAttributes<T> {}

    // type DetailedHTMLProps<E extends HTMLAttributes<T>, T> = E;

kentcdodds

{
  "name": "workshop-setup",
  "version": "1.0.0",
  "description": "This is the common setup script for most of my workshops",
  "bin": "./setup.js"
}

benawad

" Specify a directory for plugins
call plug#begin('~/.vim/plugged')

Plug 'neoclide/coc.nvim', {'branch': 'release'}
Plug 'scrooloose/nerdtree'
"Plug 'tsony-tsonev/nerdtree-git-plugin'
Plug 'Xuyuanp/nerdtree-git-plugin'
Plug 'tiagofumo/vim-nerdtree-syntax-highlight'
Plug 'ryanoasis/vim-devicons'
Plug 'airblade/vim-gitgutter'

Cyberek

So you were able to install Kodi via "sudo apt-get install kodi" but have no idea how to force it to autostart on boot?

You have tried all those googled solutions such as adding kodi-standalone to .bashrc, creating init.d script but nothing worked?

This is the right place to get the answer.

For some reason, the current version of Kodi doesnt provide 2 important files:
/etc/init.d/kodi
/etc/default/kodi

dphiffer

#!/bin/sh                                                                                                                                        

# backup.sh
# Incrementally backup the enclosing folder

# Set this to where you want your files to get backed up to (include a trailing
#   slash). This follows the same format as ssh, but you can also use a local
#   file path here.
TARGET="dphiffer@192.168.1.8:/volume1/backups/dphiffer/"

matthewmueller

# OSX for Hackers (Mavericks/Yosemite)
#
# Source: https://gist.github.com/brandonb927/3195465

#!/bin/sh

# Some things taken from here
# https://github.com/mathiasbynens/dotfiles/blob/master/.osx

# Ask for the administrator password upfront

DanHerbert

OBSOLETE

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.

Fixing npm On Mac OS X for Homebrew Users

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.

malarkey

When times get tough and people get nasty, you’ll need more than a killer smile. You’ll need a killer contract.

Used by 1000s of designers and developers Clarify what’s expected on both sides Helps build great relationships between you and your clients Plain and simple, no legal jargon Customisable to suit your business Used on countless web projects since 2008

…………………………

patsch

After I applied the latest Apple Security Update around October 20th 2012 my Java Applets would no longer work;
in particular the ATO Business Portal which I need to submit quarterly data to the Australian Taxation Office.
When using Safari I always got a "Missing Plugin" error - even after I "Enabled Java" in the Security Preferences of Safari.

I confirmed that my Java version was up to date by running:

java -version

which gave me:

brandonb927

#!/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