thiagodebastos

Concept

https://alexcabal.com/creating-the-perfect-gpg-keypair/

1. Create a regular GPG keypair. By default GPG creates one signing subkey (your identity) and one encryption subkey (how you receive messages intended for you).

2. Use GPG to add an additional signing subkey to your keypair. This new subkey is linked to the first signing key. Now we have three subkeys.

3. This keypair is your master keypair. Store it in a protected place like your house or a safe-deposit box. Your master keypair is the one whose loss would be truly catastrophic.

thiagodebastos

var  spawn = require('child_process').spawn,
un = spawn('git', ['config', 'user.name', 'Batman']),
ue = spawn('git', ['config', 'user.email', 'batman@gotham.com']),
g = spawn('git', ['commit', '-am', "Jooooooker"]);

un.stdout.on('data', function (data) {
  console.log('un stdout: ' + data);
});

ue.stdout.on('data', function (data) {

thiagodebastos

Linux

How to enable function keys

echo 0 | sudo tee /sys/module/hid_apple/parameters/fnmode

Interesting Links

https://blog.colinwaddell.com/keychron-function-keys-configuration/

thiagodebastos

var daysOfWeek = ['Monday', 'Tuesday', 'Wednesday', 'Thursday', 'Friday', 'Saturday', 'Sunday'];

var inputCalories = [3500, 1500, 1800, 2300, 2400, 1500, 1500];

// const caloriesByDay = daysOfWeek.map(function(day, index) {
//   return {
//     [day]:inputCalories[index]
//   }
// })

thiagodebastos

Keybase proof

I hereby claim:

• I am thiagodebastos on github.
• I am soulhop (https://keybase.io/soulhop) on keybase.
• I have a public key ASBgeSFYL7Al2U_jm7f9ra6ByjGe0tjx9RU3dfN0ATG98Qo

To claim this, I am signing this object:

thiagodebastos

Job Control in ZSH and Bash

All processes in ZSH/Bash under job control are in 3 states: foregrounded, backgrounded and suspended.

# run command in the foreground
command
# run commend in the background

thiagodebastos

  // Available variables:
  // - Machine
  // - interpret
  // - assign
  // - send
  // - sendParent
  // - spawn
  // - raise
  // - actions

thiagodebastos

Using git-submodules to version-control Vim plugins

If you work across many computers (and even otherwise!), it's a good idea to keep a copy of your setup on the cloud, preferably in a git repository, and clone it on another machine when you need. Thus, you should keep the .vim directory along with your .vimrc version-controlled.

But when you have plugins installed inside .vim/bundle (if you use pathogen), or inside .vim/pack (if you use Vim 8's packages), keeping a copy where you want to be able to update the plugins (individual git repositories), as well as your vim-configuration as a whole, requires you to use git submodules.

Creating the repository

Initialize a git repository inside your .vim directory, add everything (including the vimrc), commit and push to a GitHub/BitBucket/GitLab repository:

cd ~/.vim

thiagodebastos

Multiple SSH Keys settings for different github account

create different public key

create different ssh key according the article Mac Set-Up Git

$ ssh-keygen -t rsa -C "your_email@youremail.com"

thiagodebastos

const grandParent = document.getElementById("grandParent")
const parent = document.getElementById("parent")
const counter = document.getElementById("counter")
let count = 0

function increaseCounter(event) {
  event.preventDefault()
  // if we don't stop propagation, the this function will run on both event listeners, thus increasing count by 2
  // event.stopPropagation()
  count += 1