danieldogeanu

You should not use the Open SSH client that comes with Git for Windows. Instead, Windows 10 has its own implementation of Open SSH that is integrated with the system. To achieve this:

1. Start the ssh-agent from Windows Services:

• Type Services in the Start Menu or Win+R and then type services.msc to launch the Services window;
• Find the OpenSSH Authentication Agent in the list and double click on it;
• In the OpenSSH Authentication Agent Properties window that appears, choose Automatic from the Startup type: dropdown and click Start from Service status:. Make sure it now says Service status: Running.

2. Configure Git to use the Windows 10 implementation of OpenSSH by issuing the following command in Powershell:

git config --global core.sshCommand C:/Windows/System32/OpenSSH/ssh.exe

yangshun

	prettier-eslint	eslint-plugin-prettier	eslint-config-prettier
What it is	A JavaScript module exporting a single function.	An ESLint plugin.	An ESLint configuration.
What it does	Runs the code (string) through prettier then eslint --fix. The output is also a string.	Plugins usually contain implementations for additional rules that ESLint will check for. This plugin uses Prettier under the hood and will raise ESLint errors when your code differs from Prettier's expected output.	This config turns off formatting-related rules that might conflict with Prettier, allowing you to use Prettier with other ESLint configs like eslint-config-airbnb.
How to use it	Either calling the function in your code or via [prettier-eslint-cli](https://github.co

bmhatfield

# In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env
# variable pointing GPG to the gpg-agent socket. This little script, which must be sourced
# in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start
# gpg-agent or set up the GPG_AGENT_INFO variable if it's already running.

# Add the following to your shell init to set up gpg-agent automatically for every shell
if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then
    source ~/.gnupg/.gpg-agent-info
    export GPG_AGENT_INFO
else

subfuzion

Common Options

-#, --progress-bar Make curl display a simple progress bar instead of the more informational standard meter.

-b, --cookie <name=data> Supply cookie with request. If no =, then specifies the cookie file to use (see -c).

-c, --cookie-jar <file name> File to save response cookies to.

spion

Part 1: Why bubbling is good

We start with the following code

function startListening(server, cb) {
  server.listen(99999, 'localhost', cb)
}

zeroseis

• Close Android File Transfer
• Open Activity Monitor and kill “Android File Transfer Agent”
• Go to where you installed “Android File Transfer.app” (I have it under /Applications)
• Ctrl+click –> “Show package contents”
• Go to Contents/Resources
• Rename “Android File Transfer Agent” to e.g. “Android File Transfer Agent_DISABLED”
• Then go to “/Users/username/Library/Application Support/Google/Android File Transfer” and again rename the Agent app.

oleksii-zavrazhnyi

DIR=$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )

Is a useful one-liner which will give you the full directory name of the script no matter where it is being called from

These will work as long as the last component of the path used to find the script is not a symlink (directory links are OK). If you want to also resolve any links to the script itself, you need a multi-line solution:

SOURCE="${BASH_SOURCE[0]}"
while [ -h "$SOURCE" ]; do # resolve $SOURCE until the file is no longer a symlink

tonymtz

launchctl unload /Library/LaunchAgents/org.macosforge.xquartz.startx.plist
sudo launchctl unload /Library/LaunchDaemons/org.macosforge.xquartz.privileged_startx.plist
sudo rm -rf /opt/X11* /Library/Launch*/org.macosforge.xquartz.* /Applications/Utilities/XQuartz.app /etc/*paths.d/*XQuartz
sudo pkgutil --forget org.macosforge.xquartz.pkg

# Log out and log in

yetithefoot

To enable window.gc() on Chrome browser console you just need to start Chrome like this:

> /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --js-flags="--expose-gc" --enable-memory-info

Those flags enable the following console API, very usefull to debug memory leaks: 

> console.memory // print memory information
> window.gc() // force garbage collection

mitchwongho

# Assuming an Ubuntu Docker image
$ docker run -it <image> /bin/bash