how to detect ins-completion mode?

2015-07-09 Fir de Conversatie Alex Efros
Hi! I'm trying to implement starting omni completion with and then looping over completion variants also with . I've map to function which returns "\\" to start omni completion, but next should return "\" and I've no idea how to detect is user already in ins-completion mode. pumvisible() does

expand('') and conceal

2014-07-07 Fir de Conversatie Alex Efros
Hi! Is it possible to remove concealed text from result of expand('')? For example, when conceal ANSI we'll have something like: [36mfeature[0m concealed to: feature but expand('') with cursor inside "feature" will return: 36mfeature -- WBR, A

Re: Patch 7.4.264

2014-05-16 Fir de Conversatie Alex Efros
Hi! On Fri, May 16, 2014 at 12:53:17PM +0400, Nikolay Pavlov wrote: > On May 16, 2014 12:29 PM, "Alex Efros" wrote: > > > > fun s:Foo() > > > > endfun > > > > let g:Foo = function('s:Foo') > This change has nothing to do

Re: Patch 7.4.264

2014-05-16 Fir de Conversatie Alex Efros
Hi! On Fri, Apr 25, 2014 at 03:27:40PM +0200, Bram Moolenaar wrote: > > My guess right solution should be > > fun s:Foo() > > endfun > > let g:Foo = function('s:Foo') > > but I'm not 100% sure. > > That should be the right way. The more things are script-local the > better. But chec

Re: Patch 7.4.264

2014-04-25 Fir de Conversatie Alex Efros
Hi! On Fri, Apr 25, 2014 at 07:34:16PM +0400, Nikolay Pavlov wrote: > because the fact that you received a funcref never means you can call it Why is that? -- WBR, Alex. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply belo

Re: Patch 7.4.264

2014-04-25 Fir de Conversatie Alex Efros
Hi! On Fri, Apr 25, 2014 at 03:27:40PM +0200, Bram Moolenaar wrote: > > My guess right solution should be > > fun s:Foo() > > endfun > > let g:Foo = function('s:Foo') > > but I'm not 100% sure. > > That should be the right way. The more things are script-local the > better. But chec

Re: Patch 7.4.264

2014-04-24 Fir de Conversatie Alex Efros
Hi! On Thu, Apr 24, 2014 at 12:43:01PM +0200, Bram Moolenaar wrote: > > Me, too. The following used to work: > > > > fun! Foo() > > endfun > > let g:Foo = function('Foo') > > > > After 7.4.264, I get: > > " E705: Variable name conflicts with existing function: g:Foo > > That is corr

Re: esckeys affect font

2013-12-18 Fir de Conversatie Alex Efros
Hi! On Mon, Dec 16, 2013 at 04:05:47AM +0100, Tony Mechelynck wrote: > >> Like it is said under :help 'esckeys', try the following: > >> > >>:set esckeys timeout timeoutlen=5000 ttimeoutlen=100 > > If 'esckeys' makes a difference, then there is some keycode starting > with that gives a prob

esckeys affect font

2013-12-15 Fir de Conversatie Alex Efros
Hi! I'm not sure which application has this bug - vim or urxvt. I'm using urxvt with custom font which doesn't have all unicode symbols, but AFAIK urxvt somehow magically load symbols absent in current font from some other fonts. I've no idea how urxvt decide which font should be used, but looks

Re: how :help change current settings

2013-08-02 Fir de Conversatie Alex Efros
Hi! On Fri, Aug 02, 2013 at 11:40:31AM -0700, ZyX wrote: > > I've noticed :help modify current vim settings. > > For example, it does ':set nolist'. I'm trying to mimic it behavior in my > > viewdoc plugin (because it contains drop-in replacement for :help command), > > so I need to know what else

how :help change current settings

2013-08-02 Fir de Conversatie Alex Efros
Hi! I've noticed :help modify current vim settings. For example, it does ':set nolist'. I'm trying to mimic it behavior in my viewdoc plugin (because it contains drop-in replacement for :help command), so I need to know what else :help does in addition to ':set nolist'? Is this documented somewher

Re: map ZZ

2013-04-02 Fir de Conversatie Alex Efros
Hi! On Sat, Mar 30, 2013 at 01:25:07PM -0700, ZyX wrote: > Implementation really does not switch any modes, it just instead of > using something like a list of mapping tables {builtin_commands, > global_mappings, local_mappings} special-cases all built-ins and uses > plain_vgetc function in C code

map ZZ

2013-03-30 Fir de Conversatie Alex Efros
Hi! Often you wanna be able to type vim command in normal mode when keyboard layout isn't English. Some time ago :langmap was used for this, later (probably when moving to UTF-8) it was broken and replaced by usual :map (I see in doc example of :langmap with UTF-8, so probably it work now). Stran

Re: \@<= multiline bug?

2012-12-05 Fir de Conversatie Alex Efros
Hi! On Tue, Dec 04, 2012 at 08:29:39AM -0800, Ben Fritz wrote: > Maybe just match the \\\n sequences as a separate syntax item and use > nextgroup to enforce ordering. It should work (probably even a little > bit faster) and also simplify your pattern. As far as I understood, nextgroup is just a

Re: \@<= multiline bug?

2012-12-03 Fir de Conversatie Alex Efros
Hi! On Mon, Dec 03, 2012 at 05:53:58PM -0500, Benjamin R. Haskell wrote: > Probably, as it suggests there, you could just use \zs instead: > > \\\n\\\n\zsU You right, but \zs doesn't work for me. I'm writing syntax highlight rules for mkfile (OS Inferno/Plan9 variant of Makefile). It allow any a

\@<= multiline bug?

2012-12-03 Fir de Conversatie Alex Efros
Hi! Is there any reason why "\(\\\n\\\n\)\@<=U" fail to match this text: \ \ U while "\(\\\n\\\n\)U" will match it and "\(\\\n\)\@<=U" will match it too (without first line)? Vim 7.3.646, Gentoo Linux amd64 -- WBR, Alex. -- You received this message from the "vim_de

&path mangling

2012-05-31 Fir de Conversatie Alex Efros
Hi! 1) Why default &path contain /usr/include? I suppose this is compatibility/historical issue, but maybe this can be safely moved to ftplugin/c instead of default value for all files? 2) ftplugin/perl.vim: let &l:path=perlpath ftplugin/ruby.vim let &l:path = s:ruby

patch: efm_perl missed some error messages

2012-05-26 Fir de Conversatie Alex Efros
Hi! Here is patch for syntastic, but it uses exact copy of Vim's /usr/share/vim/vim73/tools/efm_perl.pl, so patch will apply: https://github.com/powerman/syntastic/commit/1e99ed56b7cefde536997c037fff44be9fd26fab -- WBR, Alex. -- You received this message from the

Re: bug related to patch 7.3.449 (Autocommands caused command to abort)

2012-05-25 Fir de Conversatie Alex Efros
Hi! On Sat, May 26, 2012 at 07:59:41AM +0200, Christian Brabandt wrote: > I don't think so, but Bram has the final saying. I would certainly find > it unexpected, if this would quit my vim. The error is simply telling > you, that an autocommand closed a window/buffer and that's why Vim > aborts

Re: bug related to patch 7.3.449 (Autocommands caused command to abort)

2012-05-25 Fir de Conversatie Alex Efros
Hi! On Thu, May 24, 2012 at 10:14:41PM +0200, Christian Brabandt wrote: > I have noticed something similar in my NrrwRgn plugin. > I am not sure, this is a bug, because at the time you issue :q the > location list ist still open and in case another window is open, :q does > not exit Vim. I'm no

bug related to patch 7.3.449 (Autocommands caused command to abort)

2012-05-24 Fir de Conversatie Alex Efros
Hi! I've discover this bug when trying to ':wq' in file with syntax errors using syntastic plugin with let g:syntastic_auto_loc_list=1 Instead of exiting from vim no matter there are syntax errors I got either E855: Autocommands caused command to abort or vim segfault. To reproduce this