- Use the present tense ("Add feature" not "Added feature")
- Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
- Limit the first line to 72 characters or less
- Reference issues and pull requests liberally after the first line
- When only changing documentation, include
[ci skip]in the commit title - Consider starting the commit message with an applicable emoji
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| -- vim: tabstop=2 shiftwidth=2 expandtab | |
| -- We almost always start by importing the wezterm module | |
| local wezterm = require 'wezterm' | |
| -- Define a lua table to hold _our_ module's functions | |
| local module = {} | |
| -- Returns a bool based on whether the host operating system's | |
| -- appearance is light or dark. | |
| function module.is_dark() |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| " Open Netrw on the directory of the current file | |
| nnoremap <leader>dd :Lexplore %:p:h<CR> | |
| " Toggle the Netrw window | |
| nnoremap <Leader>da :Lexplore<CR> | |
| if &columns < 90 | |
| " If the screen is small, occupy half | |
| let g:netrw_winsize = 50 | |
| else |
See how a minor change to your commit message style can make a difference.
git commit -m"<type>(<optional scope>): <description>" \ -m"<optional body>" \ -m"<optional footer>"
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # This file has been auto-generated by i3-config-wizard(1). | |
| # It will not be overwritten, so edit it as you like. | |
| # | |
| # Should you change your keyboard layout some time, delete | |
| # this file and re-run i3-config-wizard(1). | |
| # | |
| # i3 config file (v4) | |
| # | |
| # Please see http://i3wm.org/docs/userguide.html for a complete reference! |
Searching can be an efficient way to navigate the current buffer.
The first search commands we learn are usually / and ?. These are seriously cool, especially with the incsearch option enabled which lets us keep typing to refine our search pattern. / and ? really shine when all we want is to jump to something we already have our eyeballs on but they are not fit for every situation:
- when we want to search something that's not directly there, those two commands can make us lose context very quickly,
- when we need to compare the matches.
via (https://www.linux.com/learn/tutorials/442438-vim-tips-folding-fun)
zf#jcreates a fold from the cursor down # lines.zf/stringcreates a fold from the cursor to string .zjmoves the cursor to the next fold.zkmoves the cursor to the previous fold.zoopens a fold at the cursor.zOopens all folds at the cursor.zmincreases the foldlevel by one.zMcloses all open folds.