This is surprisingly easy...basically following Arch Wiki:
https://wiki.archlinux.org/index.php/Howdy
After some investigation, here is step by step and preferences
" ~/.vimrc | |
" ... | |
" Check syntax in Vim asynchronously and fix files, with Language Server Protocol (LSP) support | |
Plugin 'dense-analysis/ale' | |
" ... | |
" dense-analysis/ale options | |
let g:ale_history_log_output = 1 | |
let g:ale_use_global_executables = 1 |
This is surprisingly easy...basically following Arch Wiki:
https://wiki.archlinux.org/index.php/Howdy
After some investigation, here is step by step and preferences
当前wps版本 11.1.0.8722 | |
1 方法一 | |
修改配置文件 | |
nano ~/.config/Kingsoft/Office.conf | |
将 | |
[General] | |
languages= |
See how a minor change to your commit message style can make a difference.
Tip
Take a look at git-conventional-commits , a CLI util to ensure these conventions, determine version and generate changelogs
Inspiration: Deis Commit Style Guide
I often quote Deis in sections below.
It makes going back and reading commits easier. It also allows you to spend less time thinking about what your commit message should be.
rsync (Everyone seems to like -z, but it is much slower for me)