I wanted to be really able to explain to a fair amount of detail how does the program :command:`ls` actually work right from the moment you type the command name and hit ENTER. What goes on in user space and and in kernel space? This is my attempt and what I have learned so far on Linux (Fedora 19, 3.x kernel).
How does the shell find the location of 'ls' ?
| --- | |
| language: node_js | |
| node_js: | |
| - "0.12" | |
| - "iojs" | |
| sudo: false | |
| cache: | |
| directories: |
| let hasBlobConstructor = typeof(Blob) !== 'undefined' && (function () { | |
| try { | |
| return Boolean(new Blob()); | |
| } catch (e) { | |
| return false; | |
| } | |
| }()); | |
| let hasArrayBufferViewSupport = hasBlobConstructor && typeof(Uint8Array) !== 'undefined' && (function () { | |
| try { |
Let's say the plugin is at a GitHub URL https://github.com/manasthakur/foo.
First get the plugin by either cloning it (git clone https://github.com/manasthakur.foo.git) or simply downloading it as a zip (from its GitHub page).
Adding a plugin in Vim is equivalent to adding the plugin's code properly into its runtimepath (includes the $HOME/.vim directory by default).
For example, if the layout of a plugin foo is as follows:
foo/autoload/foo.vim
foo/plugin/foo.vim
| #! /bin/bash | |
| cd $(mktemp -d) | |
| wget https://aur.archlinux.org/cgit/aur.git/snapshot/insomnia.tar.gz | |
| tar xzf insomnia.tar.gz | |
| cd insomnia | |
| makepkg -s | |
| sudo pacman -U insomnia-*-x86_64.pkg.tar |
tips to evolve as a developer
developers get stuck, paralized
https://www.oreilly.com/library/view/apprenticeship-patterns/9780596806842/ch04.html
Make It Stick https://www.amazon.com.br/Make-Stick-Science-Successful-Learning/dp/0674729013