Re: Issue 215 in vim: ft=sh highlighting thinks . is a valid character in variable names.

2014-04-08 Fir de Conversatie vim
Comment #5 on issue 215 by gary@gmail.com: ft=sh highlighting thinks . is a valid character in variable names. http://code.google.com/p/vim/issues/detail?id=215 I tested it two ways: using my standard setup, which includes the setting of g:sh_noisk in my .vimrc, and the following comman

Re: Issue 215 in vim: ft=sh highlighting thinks . is a valid character in variable names.

2014-04-08 Fir de Conversatie vim
Comment #4 on issue 215 by john.b.l...@gmail.com: ft=sh highlighting thinks . is a valid character in variable names. http://code.google.com/p/vim/issues/detail?id=215 Gary commented: Setting g:sh_noisk doesn't seem to affect the syntax highlighting of '.' using Vim >7.4.236 and syntax/sh.

Re: duplicate const

2014-04-08 Fir de Conversatie Bram Moolenaar
Yukihiro Nakadaira wrote: os_unix.c: 2818 static const char const *smack_copied_attributes[] = This should be static const char *smack_copied_attributes[] or static const char * const smack_copied_attributes[] Well, which one is it? -- Just remember...if the world didn't suck, we'd a

Re: Issue 215 in vim: ft=sh highlighting thinks . is a valid character in variable names.

2014-04-08 Fir de Conversatie vim
Comment #3 on issue 215 by ewtoo...@gmail.com: ft=sh highlighting thinks . is a valid character in variable names. http://code.google.com/p/vim/issues/detail?id=215 """ The Korn shell has . in variable names; bash doesn't AFAICT, but sh.vim anticipates the problem: if you put this in your

Re: Issue 217 in vim: Cannot compile vim 7.4.238+ with Linux kernel version <= 2.6.36 due to addition of smack support.

2014-04-08 Fir de Conversatie vim
Comment #2 on issue 217 by coryom...@gmail.com: Cannot compile vim 7.4.238+ with Linux kernel version <= 2.6.36 due to addition of smack support. http://code.google.com/p/vim/issues/detail?id=217 Workaround for these platforms is to pass --disable-smack to configure. -- You received this mes

Re: Issue 217 in vim: Cannot compile vim 7.4.238+ with Linux kernel version <= 2.6.36 due to addition of smack support.

2014-04-08 Fir de Conversatie vim
Comment #1 on issue 217 by coryom...@gmail.com: Cannot compile vim 7.4.238+ with Linux kernel version <= 2.6.36 due to addition of smack support. http://code.google.com/p/vim/issues/detail?id=217 Sorry, issue topic should read kernel version < 2.6.32, not <= (it compiles fine on 2.6.36 as t

Issue 217 in vim: Cannot compile vim 7.4.238+ with Linux kernel version <= 2.6.36 due to addition of smack support.

2014-04-08 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 217 by coryom...@gmail.com: Cannot compile vim 7.4.238+ with Linux kernel version <= 2.6.36 due to addition of smack support. http://code.google.com/p/vim/issues/detail?id=217 What steps will reproduce the problem? 1. Try t

duplicate const

2014-04-08 Fir de Conversatie Yukihiro Nakadaira
os_unix.c: 2818 static const char const *smack_copied_attributes[] = This should be static const char *smack_copied_attributes[] or static const char * const smack_copied_attributes[] -- Yukihiro Nakadaira - yukihiro.nakada...@gmail.com -- -- You received this message from the "vim_d

Re: Issue 215 in vim: ft=sh highlighting thinks . is a valid character in variable names.

2014-04-08 Fir de Conversatie vim
Comment #2 on issue 215 by gary@gmail.com: ft=sh highlighting thinks . is a valid character in variable names. http://code.google.com/p/vim/issues/detail?id=215 Setting g:sh_noisk doesn't seem to affect the syntax highlighting of '.' using Vim 7.4.236 and syntax/sh.vim version 132. Re

Re: Issue 215 in vim: ft=sh highlighting thinks . is a valid character in variable names.

2014-04-08 Fir de Conversatie vim
Comment #1 on issue 215 by john.b.l...@gmail.com: ft=sh highlighting thinks . is a valid character in variable names. http://code.google.com/p/vim/issues/detail?id=215 The Korn shell has . in variable names; bash doesn't AFAICT, but sh.vim anticipates the problem: if you put this in your .

Re: Extremely slow when using relativenumber & syntax highlighting

2014-04-08 Fir de Conversatie Bram Moolenaar
Patrick Hemmer wrote: > So I enabled the 'lazyredraw' option which immensely helps vertical > movement. However horizontal movement is still terrible (and it makes > it so I cant see the cursor while holding down "l" or "h"). > > Also setting regexpengine=1 was a significant performance boost as