Alexandre Dpbm

Key bindings

So ~/.tmux.conf overrides default key bindings for many action, to make them more reasonable, easy to recall and comforable to type.

Let's go through them.

If you are an iTerm2 user, third column describes the keybinding of similar "action" in iTerm2. It's possible to reuse very same keys you already get used to and tell iTerm2 to execute analogous tmux actions. See iTerm2 and tmux integration section below.

Clean Code

Aqui estão listadas algumas das principais recomendações do livro Clean Code - Robert C. Martin, 2008

2) Meaningful Names

Use Intention-Revealing names

Avoid Disinformation

Não adicionar o tipo da variável no seu nome.
Ex: accountList.
Não utilizar nomes parecidos.

32-bit ELF binary

how to assemble and link:

nasm -f elf32 -o <filename>.o <filename>.asm
ld -m elf_i386 -o <filename> <filename>.o

template code (hello world):

section .text
global _start

The i3-wm does not come with a keybinding to lock the screen or a preconfigured auto lockscreen. This gist describes how to setup both using i3lock and xautolock. i3lock is a minimalistic lockscreen and xautolock monitors mouse and keyboard activities to automatically lock the screen after a certain time of beiing inactive.

First get the tools if neccessary. E.g. sudo apt install i3lock xautolock.

To setup the keybinding Ctrl+Alt+l (last one is a lowercase L) to lock the screen append the following lines to the i3 configuration file located at ~/.config/i3/config.

# keybinding to lock screen

Installing and Basic Programs on MPI C

Installing MPI on Ubuntu

Run the following command on terminal

$ sudo apt-get install libcr-dev mpich2 mpich2-doc

Compiling MPI Programs

Tested on Ubuntu 16.10

Clone the pyside-setup repository and init submodules

git clone https://code.qt.io/pyside/pyside-setup.git
cd pyside-setup
git submodule update --init --recursive

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules

Follow standard conventions.
Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
Boy scout rule. Leave the campground cleaner than you found it.
Always find root cause. Always look for the root cause of a problem.

	# SGR color constants
	# rene-d 2018

	class Colors:
	""" ANSI color codes """
	BLACK = "\033[0;30m"
	RED = "\033[0;31m"
	GREEN = "\033[0;32m"
	BROWN = "\033[0;33m"
	BLUE = "\033[0;34m"

	# Output a single frame from the video into an image file:
	ffmpeg -i input.mov -ss 00:00:14.435 -vframes 1 out.png

	# Output one image every second, named out1.png, out2.png, out3.png, etc.
	# The %01d dictates that the ordinal number of each output image will be formatted using 1 digits.
	ffmpeg -i input.mov -vf fps=1 out%d.png

	# Output one image every minute, named out001.jpg, out002.jpg, out003.jpg, etc.
	# The %02d dictates that the ordinal number of each output image will be formatted using 2 digits.
	ffmpeg -i input.mov -vf fps=1/60 out%02d.jpg

	# sudo /sbin/rcvboxdrv -h
	# Unloading modules:
	# Loading modules: modprobe: FATAL: Module vboxnetadp not found in directory /lib/modules/4.4.3-1-ARCH
	# modprobe: FATAL: Module vboxnetflt not found in directory /lib/modules/4.4.3-1-ARCH
	# modprobe: FATAL: Module vboxpci not found in directory /lib/modules/4.4.3-1-ARCH
	# modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/4.4.3-1-ARCH

	# Solution
	# from https://forum.antergos.com/topic/818/can-t-run-my-vitualbox/4