I just started using tmux, and i am exploring 256 color option of the
terminal.
Is there any good colorscheme that uses theses colors effectively,
especially
for C programming ?

cheers

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

On Apr 30, 1:23 pm, sinbad <sinbad.sin...@...> wrote:
> I just started using tmux, and i am exploring 256 color option of the
> terminal.
> Is there any good colorscheme that uses theses colors effectively,
> especially
> for C programming ?
>
> cheers

does guibg=#aabbcc, doesn't work in non gvim.
i am seeing two different behaviors,

hi Comment ctermfg=cyan guibg=#592929 --> this doesn't work.

but, it works in the following vimrc command.

highlight OverLength ctermbg=red ctermfg=white guibg=#592929
match OverLength /\%81v.*/

why is this behavior ?


--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

On Monday, April 30, 2012 9:55:16 PM UTC+12, sinbad wrote:
>I just started using tmux, and i am exploring 256 color option of the terminal.

Check out the CSApprox.vim plugin.
http://www.vim.org/scripts/script.php?script_id=2390

"This plugin makes GVim-only colorschemes Just Work in terminal Vim".

> does guibg=#aabbcc, doesn't work in non gvim.

Nope, gvim means gui vim.

> hi Comment ctermfg=cyan guibg=#592929 --> this doesn't work.
>
> but, it works in the following vimrc command.
>
> highlight OverLength ctermbg=red ctermfg=white guibg=#592929
> match OverLength /\%81v.*/

Forgive me if I'm pointing out the obvious, but that highlight has "ctermbg",
the first doesn't.

Regards, John

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

On Apr 30, 3:17 pm, John Little <John.B.Lit...@...> wrote:
> On Monday, April 30, 2012 9:55:16 PM UTC+12, sinbad wrote:
> >I just started using tmux, and i am exploring 256 color option of the
terminal.
>
> Check out the CSApprox.vim
plugin.http://www.vim.org/scripts/script.php?script_id=2390
>
> "This plugin makes GVim-only colorschemes Just Work in terminal Vim".
>
> > does guibg=#aabbcc, doesn't work in non gvim.
>
> Nope, gvim means gui vim.
>
> > hi Comment ctermfg=cyan guibg=#592929 --> this doesn't work.
>
> > but, it works in the following vimrc command.
>
> > highlight OverLength ctermbg=red ctermfg=white guibg=#592929
> > match OverLength /\%81v.*/
>
> Forgive me if I'm pointing out the obvious, but that highlight has "ctermbg",
the first doesn't.
>
> Regards, John

Ok, My terminal supports 256 colors, How can i use all the 256 colors
in VIM in a non gui terminal.
Obviously if the terminal supports 256 colors, there should be someway
of using it in VIM as well ?

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Hi sinbad!

On Mo, 30 Apr 2012, sinbad wrote:

> Ok, My terminal supports 256 colors, How can i use all the 256 colors
> in VIM in a non gui terminal.
> Obviously if the terminal supports 256 colors, there should be someway
> of using it in VIM as well ?

http://vim.wikia.com/wiki/256_colors_in_vim

regards,
Christian
--
Wir sind über'n Berg - es geht bergab!

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

On Mon, 2012-04-30 at 01:23 -0700, sinbad wrote:
> I just started using tmux, and i am exploring 256 color option of the
> terminal.
> Is there any good colorscheme that uses theses colors effectively,
> especially
> for C programming ?
>
> cheers
>

I use xterm16


--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

It seems that I have found the solution (after many many hours of trying :-( )

I created the function below.
The function must do this (and seems to do it):

a) when there is only 1 window:
   check if filetype is "vim"     --> Dark_ColorScheme
         if filetype is not "vim" --> Light_ColorScheme
b) when there is a split window:
    check if exist split window colorscheme variable (g:splitcolor)
    if yes, colorscheme of splitwindow = g:splitcolor

    when leaving split window:
    keep the value of the current color in g:splitcolor

Can anyone tell me if I made a mistake and if the function can be simplified?

function SetColors()
         if winnr('$') > 1
            if exists('g:splitcolor')
              exe 'colors '.g:splitcolor
            else
              exe 'colors Light_ColorScheme'
            endif
         elseif winnr('$') == 1 && &ft == 'vim'
              exe 'colors Dark_ColorScheme'
         elseif winnr('$') == 1 && &ft != 'vim'
              exe 'colors Light_ColorScheme'
         endif
endfunction
function KeepColors()
        if winnr('$') > 1
        let g:splitcolor = g:colors_name
        endif
endfunction
augroup filetype_colorscheme
         au BufEnter * call SetColors()
         au BufLeave * call KeepColors()
augroup END

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

> (...) In all cases you need
> *development* packages for every single bit of software that will be
> compiled into your application.
>
(...)

Well, the problem is: I'm not using Linux, but HP-UX and I don't know how to get
gtk-devel. I'm offered "gtk+-1.2.10", "gtk+2-2.24.10", "gtk+3-3.2.4" and all are
described as "Gimp Toolkit for creating graphical user interfaces" but nothing
beginning with gtk and ending with something like "dev" or "devel".

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

On Saturday, April 28, 2012 2:39:45 AM UTC-5, rameo wrote:
> On Friday, April 27, 2012 5:45:15 PM UTC+2, rameo wrote:
> > I still have problems mapping keys.
> >
> > On my keyboard I have these keys I want to map:
> > <C-ò>
> > <C-à>
> > <C-è>
> > <C-ù>
> > <C-ì>
> >
> > Tony once told in a message these info:
> > ò = (0xF2, o-grave) and <M-r> (Alt+0x72, Alt-r)
> > à = (0xE0, a-grave) and <M-`> (Alt+0x60, Alt-backtick)
> > è = (0xE8, e-grave) and <M-h> (Alt+0x68, Alt-h)
> > ù = (0xF9, u-grave) and <M-y> (Alt+0x79, Alt-y)
> > ì = (0xEC, i-grave) and <M-l> (Alt+0x6C, Alt-l)
> >
> > But how to combine these letters to the Ctrl key?
>
>
> When I hit Ctrl-K in insert mode followed by Ctrl-ò nothing happened.
> When I hit Ctrl-Q (I have the gvim win version) in insert mode followed by
Ctrl-ò again nothing happened.
>
> Yes ^V (+ ^K) doesn't disappear near the bottom right corner of the Vim screen
as you've indicated.
>
> Does this mean that I can't map these keys with Ctrl?
> I had to use C-Q.

Yes, as Tony said, if you press CTRL-V/CTRL-Q in insert mode, followed by your
key combination, and nothing happens, then Vim does not even get the key
sequence and you cannot map it.

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

On Monday, April 30, 2012 8:15:26 AM UTC-5, rameo wrote:
> It seems that I have found the solution (after many many hours of trying :-( )
>
> I created the function below.
> The function must do this (and seems to do it):
>
> a) when there is only 1 window:
>   check if filetype is "vim"     --> Dark_ColorScheme
>         if filetype is not "vim" --> Light_ColorScheme
> b) when there is a split window:
>    check if exist split window colorscheme variable (g:splitcolor)
>    if yes, colorscheme of splitwindow = g:splitcolor
>
>    when leaving split window:
>    keep the value of the current color in g:splitcolor
>
> Can anyone tell me if I made a mistake and if the function can be simplified?
>
> function SetColors()
>         if winnr('$') > 1
>            if exists('g:splitcolor')
>              exe 'colors '.g:splitcolor
>            else
>              exe 'colors Light_ColorScheme'
>            endif
>         elseif winnr('$') == 1 && &ft == 'vim'
>              exe 'colors Dark_ColorScheme'
>         elseif winnr('$') == 1 && &ft != 'vim'
>              exe 'colors Light_ColorScheme'
>         endif
> endfunction
> function KeepColors()
>        if winnr('$') > 1
>        let g:splitcolor = g:colors_name
>        endif
> endfunction
> augroup filetype_colorscheme
>         au BufEnter * call SetColors()
>         au BufLeave * call KeepColors()
> augroup END

Looks like it should do what you want, just fine. A minor note, you don't need
the exe if you're providing the colorscheme name literally, e.g. "exe 'colors
Dark_ColorScheme'" could be just "colors Dark_ColorScheme", but that's not
really an important detail; it should work fine as-is.

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

On Mon, Apr 30, 2012 at 07:18:31AM EDT, Christian Brabandt wrote:
> On Mo, 30 Apr 2012, sinbad wrote:

> > Ok, My terminal supports 256 colors, How can i use all the 256 colors
> > in VIM in a non gui terminal.
>
> http://vim.wikia.com/wiki/256_colors_in_vim

Provided the OP does NOT read the tip and reads Steven Black's comment
at the bottom of the page instead :-)

CJ

--
ALL YOUR BASE ARE BELONG TO US!

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Chris Jones wrote:
>>> Ok, My terminal supports 256 colors, How can i use all the 256
>>> colors in VIM in a non gui terminal.
>>
>> http://vim.wikia.com/wiki/256_colors_in_vim
>
> Provided the OP does NOT read the tip and reads Steven
> Black's comment at the bottom of the page instead :-)

Any chance of someone fixing the tip?

If the advice in the body of the tip is not helpful, please just
delete it and move what you think is good into the tip body.
Don't worry about crediting anyone because all the history is
retained and people can see what happened.

I can clean up formatting and English, but I'm not much help
with some topics, like that tip.

People can edit as an IP address, or it's easy to register an
account (enter a bogus birthdate indicating you are more than
13 years old; Google COPPA if want to know why that's needed).

John

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

On 30/04/12 10:23, sinbad wrote:
> I just started using tmux, and i am exploring 256 color option of
> the terminal. Is there any good colorscheme that uses theses colors
> effectively, especially for C programming ?
>
> cheers
>


For Vim to use 256 colours effectively, you have to make sure that t_Co
gets set to 256 when running in a 256-colour terminal, but not when in a
terminal with fewer colours (such as the Linux hardware-text console or,
I think, the Windows console, at least when in fullscreen mode).

Previous posts in this thread provide several answers to that; mine (not
necessarily the best) is simply

" use 256 colors in Console mode if we think the terminal supports it
if &term =~? 'mlterm\|xterm'
	 set t_Co=256
endif

Then you need a colorscheme which makes use of them. If you are using a
GUI-enabled Vim in console mode (which is possible on Linux but not on
Windows), you can use the CSApprox plugin, which will "translate" the
24-bit (16 million colors) gui= guibg= guifg= guisp= of any GUI-oriented
colorscheme into something as near as possible to the same colours on a
256- or 88-color terminal. (On a terminal with fewer colours, such as 8
bg + 16 fg, it will simply desist and let the cterm= ctermbg= ctermfg=
colours remain in force.) This way, if your terminal has 88 or more
colours, you'll get approximately the same look and feel as in gvim. I
like it but of course YMMV.

See also http://vim.wikia.com/wiki/Using_GUI_color_settings_in_a_terminal


Best regards,
Tony.
--
GALAHAD: No. Look, I can tackle this lot single-handed!
GIRLS:   Yes, yes, let him Tackle us single-handed!
                   "Monty Python and the Holy Grail" PYTHON (MONTY)
PICTURES LTD

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

On Tuesday, May 1, 2012 2:32:51 AM UTC+12, Arno Valentin wrote:
> ... I'm offered "gtk+-1.2.10", "gtk+2-2.24.10", "gtk+3-3.2.4" ...

IIUC, gtk+2-2.24.10 is the one you want, being gtk 2.

In my config.log, configure tries to see what version of gtk is installed by
compiling and running a gtk test programme:

configure:7987: checking for GTK - version >= 2.2.0
configure:8054: gcc -o conftest -Wall -Wshadow -Wmissing-prototypes -pthread
-I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0
-I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1
-I/usr/include/freetype2 -I/usr/include/libpng12    -I/usr/local/include 
-L/usr/local/lib conftest.c -lnsl  -pthread -lgtk-x11-2.0 -lgdk-x11-2.0
-latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo
-lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0
-lrt -lglib-2.0   >&5
configure:8054: $? = 0
configure:8054: ./conftest
configure:8054: $? = 0
configure:8069: result: yes; found version 2.24.6

If I was missing needed libraries, IIUC I'd see errors about what was missing. 
However, my config has used pkg-config; IIUC that's part of autotools which you
seem to have. It needs to work for configure to decide you've got gtk.

HTH, and regards, John

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

When I start gvim with a file name

Gvim h:\bin\pcalc.pl,
if I edit another file by name, it references the same directory...

However, if I use UNC name,
Gvim \\ishtar\home\linda\bin\pcalc.pl

to edit the same file, my current directory isn't set correctly.

I know I used to have my own script to edit files that worked
in this situation, but I don't know if vim has always been broken this way
or it is a recent  development -- maybe only on the 'x64 version

(Running vi  7.33 (2010 Aud 15, compiled Mar 25 2012 (with +perl -- though
it doesn't work with the current version of perl (5.12) as pointed to in the
email...

It seems it uses a fixed version number rather than a generic perl.dll....


Maybe it would be better to use dynamic loading, (like a 'dll') and
call it perl.dll, (as a pointer to some more specific version ... gee this
sounds similar ... I know I've seen this scheme before...)...
but then the loader can cal the dll to find out what functions are
available or
what level - and auto work with a variety of versions rather than being
statically coded to a 'dynamic' library, (!?!talk about missing the
point!)...

Oh,,, I remember the scheme...

but it was slightly different

libXXX.so =link->  lib.so.X =link->lib.so.X.Y

I think I remember it from some system that I worked on 20 or more years
ago... unix or something  ...come to think of it... I think some modern
*nixes have
similar...linux or something...

Wow....   Maybe windows could learn about using non-versioned names
(just like
linux could learn better about dynamic runtime configuration based on
available .so's, by using dlopen rather than relying on      do-or-die
initial loads....

Oh the promise of computers becoming *easier* to use -- instead...
theyv'e gone in the opposite direction due to industry failure to
preserve or value institutional knowledge...between generations...





--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

There is tips which adds code snippets of code. i talk about func
TextEnableCodeSnip
in
http://vim.wikia.com/wiki/Different_syntax_highlighting_within_regions_of_a_file

All code snips works fine. But if i enable spell after this, there is
no bad spell highlight.  Anyway, it recognize errors (z= works).

How i can fix it ? (to use snips and spell option in same file and
have spell bad highlight).

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

I seem to have trouble with the matchtime option. As I understand it,
this option will show the matching-brace highlight for a short time,
then disappear. I cannot get this option to work, instead in all
environments the matching brace is highlighted indefinitely. I am
trying in these environments:

Konsole in KDE 4.7 and VIM 7.3
Konsole in KDE 4.7 SSHing into CentOS 5.x with VIM 7.0
Putty in Windows XP SSHing into CentOS 5.x with VIM 7.0
GVIM 7.3 in Windows XP
A recent Cygwin on Windows XP with VIM, I did not check the version
though and I no longer have access to it
Cygwin on Windows XP SSHing into CentOS 5.x with VIM 7.0

I have this in .vimrc on all the environments that I tried:
set showmatch
set matchtime=10

Is this not the right way to use matchtime, or am I understanding the
option incorrectly?

Thanks.

--
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

On Wed, Mar 7, 2012 at 23:18, Charles Campbell
<Charles.E.Campbell@...> wrote:
> Yes, its back!
>
> Albeit at a new webhost (apply your favorite search engine to hostbig).  You
> may find it at:
>
> http://www.drchip.org/
>
> Hopefully all my vim pages and content are there and accessible.  Let me
> know if there's problems/something missing.
>
> Chip Campbell
>

I see that I'm late to the party, but let me say thank you Chip. I am
learning quite a lot from your VIM page.

--
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

On Tuesday, May 1, 2012 10:00:56 PM UTC+12, dotancohen wrote:
> ... in all environments the matching brace is highlighted indefinitely...

That appears to be matchparen, a "standard plugin".

See :h matchparen

I mostly don't like it, so put

     let g:loaded_matchparen = 1

in my .vimrc to suppress it.

Regards, John

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

When using the spell correction feature ("set spelllang=de_de spell") a word
containing a german "ß" (0xDF) is displayed incorrectly if it is found to be
misspelled:

Wir wohnen nicht in der >>>Georgenkirchstraße<<<, sondern in der
>>>Hauptstraße<<<.

In this sample "Georgenkirchstraße" is flagged as misspelled (as opposed to
"Hauptstraße") - which would be ok - but the "ß" in the flagged word is not
considered as a valid word character; hence the word cannot be directly added
(w/o creating a selection) to the exception list with e.g. "zg".

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

On Tue, May 1, 2012 at 14:28, John Little <John.B.Little@...> wrote:
> On Tuesday, May 1, 2012 10:00:56 PM UTC+12, dotancohen wrote:
>> ... in all environments the matching brace is highlighted indefinitely...
>
> That appears to be matchparen, a "standard plugin".
>
> See :h matchparen
>
> I mostly don't like it, so put
>
>    let g:loaded_matchparen = 1
>
> in my .vimrc to suppress it.
>
> Regards, John
>

Thank you John. I have suppressed the matchparen as you mention, but I
would still like to have the highlight show for one second. The
showmatch and matchtime options are still not working. Can I enable
them somehow?

Thanks.

--
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Dotan Cohen wrote:
> On Wed, Mar 7, 2012 at 23:18, Charles Campbell
> <Charles.E.Campbell@...>  wrote:
>
>> Yes, its back!
>>
>> Albeit at a new webhost (apply your favorite search engine to hostbig).  You
>> may find it at:
>>
>> http://www.drchip.org/
>>
>> Hopefully all my vim pages and content are there and accessible.  Let me
>> know if there's problems/something missing.
>>
>> Chip Campbell
>>
>>
> I see that I'm late to the party, but let me say thank you Chip. I am
> learning quite a lot from your VIM page.
>
>
You're welcome!
Chip Campbell

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Dotan Cohen, Tue 2012-05-01 @ 15:14:08+0300:
> I have suppressed the matchparen as you mention, but I would still
> like to have the highlight show for one second. The showmatch and
> matchtime options are still not working. Can I enable them somehow?

The highlighting you are used to is provided by the matchparen plugin.
'showmatch' and 'matchtime' are, on the other hand, for Vim's built-in
(i.e. not implemented as a plugin) matching functionality, which, rather
than highlighting, jumps the cursor to the matching opening
brace/bracket/parenthesis for a brief time after the closing character
in the pair is typed. Try typing some opening and closing parentheses
after `:set showmatch` and you'll see what I mean. This feature is
turned off by default.

As far as I know, the matchparen plugin does not refer to the
'matchtime' option to determine how long to highlight; it is either on
indefinitely or it is off. Barring modification to the plugin itself, I
don't think there's any way to get precisely what you want.

On Tue, May 1, 2012 at 17:39, Taylor Hedberg <tmhedberg@...> wrote:
>
> The highlighting you are used to is provided by the matchparen plugin.
> 'showmatch' and 'matchtime' are, on the other hand, for Vim's built-in
> (i.e. not implemented as a plugin) matching functionality, which, rather
> than highlighting, jumps the cursor to the matching opening
> brace/bracket/parenthesis for a brief time after the closing character
> in the pair is typed. Try typing some opening and closing parentheses
> after `:set showmatch` and you'll see what I mean. This feature is
> turned off by default.
>
> As far as I know, the matchparen plugin does not refer to the
> 'matchtime' option to determine how long to highlight; it is either on
> indefinitely or it is off. Barring modification to the plugin itself, I
> don't think there's any way to get precisely what you want.

Thanks Taylor, I see it now. I was testing with existing code,
expecting to put the cursor on a brace and see the match. I now
understand that it only works for typing out new code.

Is there any way to change the behaviour of the matchparen plugin to
underline the matching brace, instead of highlighting it? I often get
confused which is the highlighted brace and which brace has the
cursor.

Thanks.

--
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Dotan Cohen, Tue 2012-05-01 @ 19:05:21+0300:
> Is there any way to change the behaviour of the matchparen plugin to
> underline the matching brace, instead of highlighting it? I often get
> confused which is the highlighted brace and which brace has the
> cursor.

matchparen uses the MatchParen highlight group to highlight the matching
character, so you can modify that group to change how it appears.

For instance, in my Vim, running in a color terminal, I can do the
following to remove the highlighting effect and just underline instead:

     :highlight MatchParen ctermbg=NONE ctermfg=NONE cterm=underline

You would need to tweak the above if you use the GUI version or a
non-color terminal, but the idea is the same. See `:help :highlight` for
details.

Dotan Cohen wrote:
> On Tue, May 1, 2012 at 17:39, Taylor Hedberg<tmhedberg@...>  wrote:
>
>> The highlighting you are used to is provided by the matchparen plugin.
>> 'showmatch' and 'matchtime' are, on the other hand, for Vim's built-in
>> (i.e. not implemented as a plugin) matching functionality, which, rather
>> than highlighting, jumps the cursor to the matching opening
>> brace/bracket/parenthesis for a brief time after the closing character
>> in the pair is typed. Try typing some opening and closing parentheses
>> after `:set showmatch` and you'll see what I mean. This feature is
>> turned off by default.
>>
>> As far as I know, the matchparen plugin does not refer to the
>> 'matchtime' option to determine how long to highlight; it is either on
>> indefinitely or it is off. Barring modification to the plugin itself, I
>> don't think there's any way to get precisely what you want.
>>
> Thanks Taylor, I see it now. I was testing with existing code,
> expecting to put the cursor on a brace and see the match. I now
> understand that it only works for typing out new code.
>
> Is there any way to change the behaviour of the matchparen plugin to
> underline the matching brace, instead of highlighting it? I often get
> confused which is the highlighted brace and which brace has the
> cursor.
>
In quickly diving into matchparen, I see that the matching brace is the
MatchParen highlighting group.

Consequently,

    hi clear MatchParen
    hi MatchParen gui=underline cterm=underline

should do the trick.  When you're  happy with it, put these two lines into

.vim/after/plugin/matchparen.vim

Regards,
Chip Campbell

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

On Tue, May 1, 2012 at 19:15, Charles Campbell
<Charles.E.Campbell@...> wrote:
> In quickly diving into matchparen, I see that the matching brace is the
> MatchParen highlighting group.
>
> Consequently,
>
>  hi clear MatchParen
>  hi MatchParen gui=underline cterm=underline
>
> should do the trick.  When you're  happy with it, put these two lines into
>
> .vim/after/plugin/matchparen.vim
>
> Regards,
> Chip Campbell

Thank you Chip. That does exactly what I need! I will also take your
example and try my hand at "delving" into the matchparen plugin to
learn a bit about how this is done.

Thanks!

--
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

I have vimrc and copy of ~/.vim/ with all plugins -- but i can not migrate this
settings on clear version vim (fresh install). Why vim does not include plugin
after copy them into ./vim ?

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

On Tuesday, May 1, 2012 11:51:14 AM UTC-5, äÍÉÔÒÉÊ äÏÌÇÏ× wrote:
> I have vimrc and copy of ~/.vim/ with all plugins -- but i can not migrate
this
> settings on clear version vim (fresh install). Why vim does not include plugin
> after copy them into ./vim ?

What system are you on? Windows looks in $HOME/vimfiles, not $HOME/.vim.

Check your 'runtimepath' setting to see where Vim will look for plugins if
you're still in doubt.

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

On Fri, Apr 27, 2012 at 12:16 PM, Ben Fritz <fritzophrenic@...> wrote:
> On Friday, April 27, 2012 10:02:11 AM UTC-5, Justin wrote:
>> Running ":verbose set ft? autoindent? smartindent? cindent? cino?"
>> from my Vim it says:
>>
>>   filetype=cpp
>>         Last set from /usr/local/share/vim/vim70/filetype.vim
>>   autoindent
>>         Last set from ~/.vimrc
>>   smartindent
>>         Last set from ~/.vimrc
>>   cindent
>>         Last set from /usr/local/share/vim/vim70/indent/cpp.vim
>>   cinoptions=(0
>>         Last set from ~/.vimrc
>>
>> I tried adding W2s to my cinoptions like you have, as well as setting
>> noautoindent and nosmartindent, but I still have the problem.
>> Hmm... maybe the cindent and cinoptions get set differently between
>> vim 7.0 and 7.3?
>>
>>
>
> Maybe. Checking the help, I think I understand:
>
> autoindent has no effect if smartindent, cindent, or indentexpr is set
> smartindent has no effect if cindent or indentexpr is set
> cindent has no effect if indentexpr is set
>
> So, also check the value of indentexpr. If that doesn't fix your issue, try
upgrading your Vim version. You don't mention your system, but it is quite
likely there's a more recent version available through your normal download
means, or you can always build from source.
>
> http://vim.wikia.com/wiki/Download
>
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php

Thanks so much for your help!  Just to let you know, it was Vim
version 7.0 that was causing the problems.  I upgraded to 7.3 and the
block indenting is working like a champ now with the exact same config
and plugins I was running earlier!  Thanks again!

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php