Re: Quickfix List vs Location List

Hi all, On Mon, Aug 8, 2016 at 4:37 PM, Yegappan Lakshmanan wrote: > >> >> By the way, I remember some patches that add functions returning >> information about buffer/window/tabpage. It would be logical if >> information regarding whether given buffer contains >>

Update to YAML indent file

I found that YAML indent file is incorrect in some cases: specifically s:FindPrevLessIndentedLine incorrectly ignores some non-comment line while finding comment lines, `#key:` line may be considered a valid mapping entry, indent script may think that line that follows `key: ~` is a part of the

Re: <M-"> broken by patch 7.4.1968

Stephen Riehm wrote: > Hi everyone, > > after upgrading from MacVim 104 to MacVim 106 I noticed that no longer > works (not recognised for maps - just inserts a ¢ character). (The problem > also exists in 105 - which I missed). > > Workarounds such as also

Re: gvim and ASCII glyphs

On Saturday, 13 August 2016 19:55:23 UTC+2, manuelschi...@googlemail.com wrote: > On Thursday, 11 August 2016 19:30:57 UTC+2, Stefan Schwarzer wrote: > > On 2016-08-11 17:40, Kazunobu Kuriyama wrote: > > > 2016-08-11 23:44 GMT+09:00 Ken Takata : > > >> Screenshot

Re: Patch 7.4.2207

And the missing text: Patch 7.4.2207 Problem:The +xpm feature is not sorted properly in :version output. Solution: Move it up. (Tony Mechelynck) Files: src/version.c -- hundred-and-one symptoms of being an internet addict: 23. You can't call your mother...she doesn't have a modem.

Re: gvim and ASCII glyphs

On Thursday, 11 August 2016 19:30:57 UTC+2, Stefan Schwarzer wrote: > On 2016-08-11 17:40, Kazunobu Kuriyama wrote: > > 2016-08-11 23:44 GMT+09:00 Ken Takata : > >> Screenshot attached. (I haven't try PragmataPro.) > > > > I don't either for an obvious reason..Isn't

Re: [patch][doc] Update documents

Ken Takata wrote: > I found some mistakes in the documents. Please check the attached patches: > > * Mention funcref() not only function(). > * Fix typos. > * Direct-X should be DirectX. > * Change "." to ".". If tabs are used, the layout can be > wrong especially when conceal is used.

Patch 7.4.2207

*** ../vim-7.4.2206/src/version.c 2016-08-13 15:29:10.447871215 +0200 --- src/version.c 2016-08-13 16:37:27.193960314 +0200 *** *** 724,729 --- 724,742 #else "-xim", #endif + #ifdef WIN3264 + # ifdef FEAT_XPM_W32 + "+xpm_w32", + # else +

Re: +/-xpm or +/-xpm_w32 out of sequence in :version (with patch)

Tony Mechelynck wrote: > Problem: +xpm (or -xpm or +/-xpm_w32) is out of sequence in the output > of :version > Solution: reorder the set of features in src/version.c Thanks. > Note: The attached patch ("git-style" IIUC, but made from my clone of > the Mercurial mirror) has been written with

Re: [patch][doc] Update documents

Ken Takata wrote: > 2016/8/13 Sat 8:50:59 UTC+9 Ken Takata wrote: > > Hi, > > > > I found some mistakes in the documents. Please check the attached patches: > > > > * Mention funcref() not only function(). > > * Fix typos. > > * Direct-X should be DirectX. > > * Change "." to ".". If tabs

Patch 7.4.2206

Patch 7.4.2206 Problem:Warning for unused function. Solution: Put the function inside #ifdef. (John Marriott) Files: src/evalfunc.c *** ../vim-7.4.2205/src/evalfunc.c 2016-08-13 15:07:38.347640696 +0200 --- src/evalfunc.c 2016-08-13 15:27:16.444905363 +0200 ***

Re: Patch 7.4.2200

John Marriott wrote: > On 13-Aug-2016 12:29 AM, Bram Moolenaar wrote: > > Patch 7.4.2200 > > Problem:Cannot get all information about a quickfix list. > > Solution: Add an optional argument to get/set loc/qf list(). (Yegappan > > Lakshmanan) > > Files:

Patch 7.4.2205

Patch 7.4.2205 Problem:'wildignore' always applies to getcompletion(). Solution: Add an option to use 'wildignore' or not. (Yegappan Lakshmanan) Files: runtime/doc/eval.txt, src/evalfunc.c, src/testdir/test_cmdline.vim *** ../vim-7.4.2204/runtime/doc/eval.txt2016-08-12

Re: getcompletion() and 'wildignore' setting

Yegappan wrote: > >> >> The getcompletion() function applies the 'wildignore' option setting > >> >> and removes all the entries matching the file patterns in > >> >> 'wildignore'. Currently, there is no way to disable this. Do you think > >> >> we should add a 'flag' argument to getcompletion()