See how a minor change to your commit message style can make you a better programmer.
Format: <type>(<scope>): <subject>
<scope> is optional
| [ | |
| { | |
| "key": "h", | |
| "command": "editor.action.scrollLeftHover", | |
| "when": "editorHoverFocused" | |
| }, | |
| { | |
| "key": "j", | |
| "command": "editor.action.scrollDownHover", | |
| "when": "editorHoverFocused" |
| { | |
| "vim.smartRelativeLine": true, | |
| "editor.cursorSurroundingLines": 8, | |
| "editor.wordSeparators": "`~!@#$%^&*()=+[{]}\\|;:'\",.<>/?", | |
| "vim.leader": "<space>", | |
| "vim.normalModeKeyBindings": [ | |
| { | |
| "before": ["<leader>", "e"], | |
| "commands": ["workbench.view.explorer"] | |
| }, |
| function stringToColor(string) { | |
| let hash = 0; | |
| let i; | |
| for (i = 0; i < string.length; i += 1) { | |
| hash = string.charCodeAt(i) + ((hash << 5) - hash); | |
| } | |
| let color = '#'; |
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent| DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE | |
| Version 2, December 2004 | |
| Copyright (C) 2011 Jed Schmidt <http://jed.is> | |
| Everyone is permitted to copy and distribute verbatim or modified | |
| copies of this license document, and changing it is allowed as long | |
| as the name is changed. | |
| DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE |