Fish is a smart and user-friendly command line (like bash or zsh). This is how you can instal Fish on MacOS and make your default shell.
Note that you need the https://brew.sh/ package manager installed on your machine.
brew install fish
| import string | |
| import sys | |
| import requests | |
| import whois | |
| from nltk import tokenize | |
| BOOKFILE = sys.argv[1] | |
| OUTPUTFILE = BOOKFILE + '.possible-domains.txt' |
Fish is a smart and user-friendly command line (like bash or zsh). This is how you can instal Fish on MacOS and make your default shell.
Note that you need the https://brew.sh/ package manager installed on your machine.
brew install fish
| # Description: Boxstarter Script | |
| # Author: Jess Frazelle <jess@linux.com> | |
| # Last Updated: 2017-09-11 | |
| # | |
| # Install boxstarter: | |
| # . { iwr -useb http://boxstarter.org/bootstrapper.ps1 } | iex; get-boxstarter -Force | |
| # | |
| # You might need to set: Set-ExecutionPolicy RemoteSigned | |
| # | |
| # Run this boxstarter by calling the following from an **elevated** command-prompt: |
| #!/usr/bin/env ruby | |
| require 'optparse' | |
| require 'erb' | |
| class GeneratesConfig | |
| attr_accessor :repo_dir, :output_file, :host, :port | |
| def initialize | |
| @host = "localhost" |
rails new <project_name> -d postgresql --skip-turbolinks --skip-spring -T-d postgresql sets up the project to use PostgreSQL--skip-turbolinks & --skip-spring creates a project that does not use turbolinks or spring-T skips the creation of the test directory and use of Test::Unit| #!/usr/bin/env ruby | |
| require "rubygems" | |
| require "twitter" | |
| require "json" | |
| require "faraday" | |
| # things you must configure | |
| TWITTER_USER = "your_username" | |
| # get these from dev.twitter.com |
rails new <project_name> -d postgresql --skip-turbolinks --skip-spring -T-d postgresql sets up the project to use PostgreSQL--skip-turbolinks & --skip-spring creates a project that does not use turbolinks or spring-T skips the creation of the test directory and use of Test::UnitPutting cryptographic primitives together is a lot like putting a jigsaw puzzle together, where all the pieces are cut exactly the same way, but there is only one correct solution. Thankfully, there are some projects out there that are working hard to make sure developers are getting it right.
The following advice comes from years of research from leading security researchers, developers, and cryptographers. This Gist was [forked from Thomas Ptacek's Gist][1] to be more readable. Additions have been added from
Just migrated it from Codepen.io to markdown. Credit goes to David Conner.
| Working with DOM | Working with JS | Working With Functions |
|---|---|---|
| Accessing Dom Elements | Add/Remove Array Item | Add Default Arguments to Function |
| Grab Children/Parent Node(s) | Add/Remove Object Properties | Throttle/Debounce Functions |
| Create DOM Elements | Conditionals |
| require "rubygems" | |
| require "twitter" | |
| require "json" | |
| # things you must configure | |
| TWITTER_USER = "your_username" | |
| MAX_AGE_IN_DAYS = 1 # anything older than this is deleted | |
| # get these from dev.twitter.com | |
| CONSUMER_KEY = "your_consumer_key" |