ludoo0d0a

VERSION=1.0
EMAIL=my.name@yourmail.com

echo "Creating an SSH key for you..."
ssh-keygen -t rsa -b 4096 -C "$EMAIL"

echo "Please add this public key to Github \n"
echo "https://github.com/account/ssh \n"
read -p "Press [Enter] key after this..."

ludoo0d0a

#!/bin/bash

#
# Flutter upgrade from a fresh install
# version : 1.0
# Can be used in case of androidX migration.
# ios, Android specific configruation are not copied ; use a git merge after execution
#
# Copy this file in /usr/local/bin/ and call it from root source of an existing flutter project.
# It requires : jq, xq and yq installation 

MacKentoch

unpair wearOS watch wihtout performing factory reset (and without root)

1- Wear is connected with phone A (old phone or the same phone before a factory reset) so turn off Bluetooth on this phone.

2- enable developer mode on watch, manually go:

• settings > system > about and tap build version 10 times

3- reset previously paired phone (phone A) then watch will restart:

adb shell "pm clear com.google.android.gms && reboot"

ralfr

Description

Based on info from http://peterdowns.com/posts/open-iterm-finder-service.html but with modified behavior and fixed to work with iTerm2 version 3 or later. It will not work with older versions of iTerm. The modified behavior is to open a new terminal window for each invocation instead of reusing an already open window. Update - The original author released a build script for the newer iTerm2 versions at https://github.com/peterldowns/iterm2-finder-tools that keeps the original behavior of reusing an open iTerm2 window.

To open iTerm2 at selected folder with keyboard shortcut

1. Run Automator, select a new Service
2. Select Utilities -> Run AppleScript
3. Service receives selected 'folders' in 'finder.app'
4. Paste script:

dchowitz

Debugging ES6 in VS Code

My current editor of choice for all things related to Javascript and Node is VS Code, which I highly recommend. The other day I needed to hunt down a bug in one of my tests written in ES6, which at time of writing is not fully supported in Node. Shortly after, I found myself down the rabbit hole of debugging in VS Code and realized this isn't as straightforward as I thought initially. This short post summarizes the steps I took to make debugging ES6 in VS Code frictionless.

What doesn't work

My first approach was a launch configuration in launch.json mimicking tape -r babel-register ./path/to/testfile.js with babel configured to create inline sourcemaps in my package.json. The debugging started but breakpoints and stepping through the code in VS Code were a complete mess. Apparently, ad-hoc transpilation via babel-require-hook and inline sourcemaps do not work in VS Code. The same result for attaching (instead of launch) to `babel-node

tonysneed

- Open Automator 
- File -> New -> Service 
- Change "Service Receives" to "files or folders" in "Finder" 
- Add a "Run Shell Script" action 
- Change "Pass input" to "as arguments" 
- Paste the following in the shell script box: open -n -b "com.microsoft.VSCode" --args "$*" 
- Save it as something like "Open in Visual Studio Code"

royclarkson

#!/bin/bash
for ((PORT=5554; PORT<=5584; PORT+=2)); do
    echo killing emulator-$PORT...
    adb -s emulator-$PORT emu kill
done

CristinaSolana

1. Clone your fork:

git clone git@github.com:YOUR-USERNAME/YOUR-FORKED-REPO.git

2. Add remote from original repository in your forked repository:

cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream

andyedinborough

/*
MIT License (MIT)
Copyright (c) 2011 Andy Edinborough

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH TH