跳到主要內容

VIM on Windows

I have done with the slowness of cygwin git and switch to git-for-windows. Unfortunately, vim on cygwin doesn’t work well with git-for-windows per various path problems (e.g. plugin, path delimiters, etc). Here are some notes for tweaking vim on Windows.

  1. .vim or vimfiles Directories?
    Later one is used on Windows, however, many plugin or your scripts may refer the previous one. Thus, mklink it! i.e. .vim <==> vimfiles.

  2. VIM with Python Support
    Official vim81 compiles vim.exe without python support and gvim.exe with python/dyn (verify that with gvim --version). Thus, Python support is only avail as of gvim.exe per official packages.
    Assume python.exe and python27.dll was installed in C:\Python\bin
    Add following environment variables

    PYTHONHOME=C:\Python\bin
PATH=%PATH%;%PYTHONHOME%

    For :h pythonhome and :h pythondll .
    Verify above settings with :python print ''.

  3. Color Scheme
    gvim requires true color to apply color scheme correctly. Convert your cterm scheme with this script (not mine work).
    Place scheme files in %HOME%\vimfiles\color. Windows equivalent of $HOME\.vim on Unix. Note that %HOME%\.vimrc still works.

  4. gtags
    Jason Hood provides wonderful pre-built gtags for Windows. Download and unzip it. Then add its bin directory to your %PATH%.

  5. gvim specific settings
    Place them in .gvimrc

    set guifont=Consolas:h10:cANSI
" (not really) maximize window at start
set lines=999 columns=999

Written with StackEdit.

標籤：

留言

張貼留言

這個網誌中的熱門文章

得利油漆色卡編碼方式

得利油漆色卡編碼方式 類似 Munsell 色彩系統 ，編碼方式為 HUE LRV/CHROMA 例如 10GY 61/449 ( 色卡 ) 編碼數值 描述 10GY hue ，色輪上從 Y(ellow) 到 G(reen) 區分為 0 ~ 99 ，數值越小越靠近 Y，越大越靠近 G 61 LRV (Light Reflectance Value) 塗料反射光源的比率，數值從 0% ~ 100% ，越高越亮，反之越暗，也可理解為明度 449 chroma 可理解為彩度，數值沒有上限，越高顏色純度 (濃度) 越高 取決於測量儀器，對應至 RGB 並不保證視覺感受相同。 參考資料： 色卡對照網站 e-paint.co.uk Written with StackEdit .
張貼留言
閱讀完整內容

C++17 新功能 try_emplace

C++17 新功能 try_emplace 回顧 emplace 大家的好朋友 Standard Template Library (STL) 容器提供如 push_back , insert 等介面，讓我們塞東西進去； C++11 之後，新增了 emplace 系列的介面，如 std::vector::emplace_back , std::map::emplace 等，差異在於 emplace 是在容器內 in-place 直接建構新元素，而不像 push_back 在傳遞參數前建構，下面用實例來說明： struct Value { // ctor1 Value ( int size ) : array ( new char [ size ] ) , size ( size ) { printf ( "ctor1: %d\n" , size ) ; } // ctor2 Value ( const Value & v ) : array ( new char [ v . size ] ) , size ( v . size ) { printf ( "ctor2: %d\n" , size ) ; memcpy ( array . get ( ) , v . array . get ( ) , size ) ; } private : std :: unique_ptr < char [ ] > array ; int size = 0 ; } ; struct Value 定義了自訂建構子 (ctor1)，以指定大小 size 配置陣列，複製建構子 (ctor2) 則會配置與來源相同大小及內容的陣列，為了方便觀察加了一些 printf 。當我們如下使用 std::vector::push_back 時 std :: vector < Value > v ; v . push_back ( Value ( 2048 ) ) ; 首先 Value 會先呼叫 ctor1，傳給 push_ba...
張貼留言
閱讀完整內容

Notes for C/C++ Programming

Notes for C/C++ Programming Notes for C/C++ Programming Off by One Error Prone # define LEN 128 char buf [ LEN ] = { 0 } ; // -1 for prevent missing NULL terminator // since strncpy doesn't preserve it for us. strncpy ( buf , something , sizeof ( buf ) - 1 ) ; // snprintf does preserve NULL terminator for us // i.e. actual size for placing characters is sizeof(buf) - 1 // but it takes extra time to parsing format snprintf ( buf , sizeof ( buf ) , something ) ; Bad things often happen when we mess with -1 or +1 to pointers point to continuous elements. Absorber # define LEN 128 char buf [ LEN + 1 ] = { 0 } ; // ^^^^ Always preserve 1 byte strncpy ( buf , somethin , sizeof ( buf ) ) ; Constant Correctness (C/C++) Bad void do_something ( char * dest , char * src ) ; struct MyList { void do_something ( std :: string & name ) ; } ; Reason : Will the name be modified by the lookup method? Will stat...
張貼留言
閱讀完整內容