mustermann, max | 20 Dec 18:36 2014

modify "tab indent markers"

Hello guys,

i have installed this vim distribution here: http://vim.spf13.com/ and i 
like to know, how i can make these greyish/white "tab indent markers" 
less visible (=> darker), and what command in the vimrc is responsible 
for this.

Thanks a lot.

kind regards and merry christmas :3

-- 
--

-- 
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

--- 
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe <at> googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Paolo Bolzoni | 20 Dec 19:04 2014
Picon

Smarter sintax coloring

I program in C++ using vim and, as most developers, I use syntax
coloring. I have a weak spot for colorful terminal screens...

However, I have the feeling that syntax coloring is little more
than eye candy.

Lets see this two lines of code:

a -= b;

against

a =- b;

The meaning is totally different, yet coloring won't help you at all.

It is possible to setup syntax coloring so different operators
have a different color?

Yours faithfully,
Paolo

-- 
--

-- 
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

--- 
You received this message because you are subscribed to the Google Groups "vim_use" group.
(Continue reading)

ping song | 20 Dec 18:16 2014
Picon

vim: stock trading plugin

http://bluegene8210.is-programmer.com/user_files/bluegene8210/Image/Screenshot%20from%202014-11-05%2022:39:33.png

whatelse vim can't do?

-- 
--

-- 
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

--- 
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe <at> googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Marco Bernardo | 19 Dec 16:04 2014
Picon

problem with Gvim 7.4 on Linux Ubuntu 12.04: random number of lines

When I use Gvim 7.4 on my laptop with Linux Ubuntu 12.04,
the window is opened with a random number of lines.

My .virmc file is:

    set gfn=Courier\ 10\ Pitch\ 11
    set lines=30
    set columns=109
    set textwidth=108

and my .gvimrc file is:

    set ghr=50
    colorscheme darkblue

The window is sometimes opened with 30 lines (which is what I want)
and other times with 26 only.

I tried to change the value of ghr, but nothing good happened.

Can you please help me with this?

Best regards,
 		Marco Bernardo

Marco Bernardo | 19 Dec 15:52 2014
Picon

problem with Gvim 7.4 on Linux Ubuntu 12.04: random number of lines

When I use Gvim 7.4 on my laptop with Linux Ubuntu 12.04,
the window is opened with a random number of lines.

My .virmc file is:

    set gfn=Courier\ 10\ Pitch\ 11
    set lines=30
    set columns=109
    set textwidth=108

and my .gvimrc file is:

    set ghr=50
    colorscheme darkblue

The window is sometimes opened with 30 lines (which is what I want)
and other times with 26 only.

I tried to change the value of ghr, but nothing good happened.

Can you please help me with this?

Best regards,
 		Marco Bernardo

Tim Chase | 19 Dec 16:02 2014

Re: How to use bufdo?

[copying the mailing list as you seem to have just replied to me
personally -- my own knowledge is limited, so it's good to tap the
communal brain in case you stump me]

On 2014-12-19 09:03, Ven Tadipatri wrote:
> Hmm...I probably should have explained my scenario more clearly.
> I have 2 buffer windows open that I have not saved to a file and
> wanted to do a "grep -v" rather than a grep.

Ah, I can only give you answers to the questions you ask. ;-)

For this scenario, I'd use

  :set hidden
  :bufdo v/pattern/d

then, if everything looked copacetic, I would issue

  :wa

to write all the modified buffers.  If not, I believe that issuing

  :bufdo u

will undo all the changes in each buffer (there might be weirdness if
you'd modified a buffer prior to issuing the "bufdo" command, and
then the bufdo command didn't make any changes in that buffer, it
would undo your prior change instead of your filtering change)

> It seems like the bufdo g/somestring/ command prints out the results
(Continue reading)

Bram Moolenaar | 19 Dec 15:27 2014
Picon
Picon

Vim 2015 calendar available


Hello Vim users,

I have updated the handy desktop calendar for 2015.  It prints on one
sheet of paper and, after folding and applying a bit of glue, stands on
your desk.

It is available in English and Dutch.  You can find the PDF files on my
website: http://moolenaar.net/#Calendar

If you are doing your Christmas shopping on Amazon, please consider
using the links on this page: http://www.iccf.nl/click1.html
A percentage of the sales will go to Vim's charity, helping children in
Uganda, and it doesn't cost you anything.

Otherwise, consider making a donation: http://www.iccf.nl/donate.html
And for a very special Christmas present: Sponsor a child!
http://www.iccf.nl/sponsor.html

Happy Vimming!

--

-- 
I started out with nothing, and I still have most of it.
                                -- Michael Davis -- "Tonight Show"

 /// Bram Moolenaar -- Bram <at> Moolenaar.net -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org        ///
 \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

(Continue reading)

Ven Tadipatri | 18 Dec 17:26 2014
Picon

How to use bufdo?

So I just learned about a cool new command called 'bufdo' where you
can execute a command across multiple buffers.  Unfortunately, I can't
quite get it to work.
I've got 2 buffers open side by side (this is output I've piped to vi,
so it's not saved in any file) and I want to grep for "somestring" in
both.

:bufdo !grep somestring

It breaks out of vi with a message
"[No write since last change]"

After hitting enter/ctrl+c a couple of times, I'm back into vi, but
nothing's changed.
I don't want vi to save anything, I just want it to grep for the
matching lines in the 2 buffers I have open.

I tried playing around with these:
:set autowriteall
:set hidden

But that didn't work either...so how do a simple grep across buffers
without having to save?

Thanks,
Ven

-- 
--

-- 
You received this message from the "vim_use" maillist.
(Continue reading)

BPJ | 15 Dec 12:09 2014
Picon

Can the "<" char be escaped with a backslash in Vim keymaps?

Can the "<" (less-than/left angle bracket) char be escaped with backslash in Vim keymaps? Or to put it
otherwise: which characters can be escaped with a backslash in a keymap? 

:help mbyte-keymap says:

# The lines after "loadkeymap" are interpreted with 'cpoptions' set to "C".
# This means that continuation lines are not used and a backslash has a special
# meaning in the mappings.  Examples: >
#
# 	" a comment line
# 	\"	x	maps " to x
# 	\\	y	maps \ to y

but I seem to remember having used `\<` and it worked. I guess that's what is implied by "Examples"?

The reason I'm asking is that I'm writing something which parses keymaps and turns them into another
something which a third something can use to transliterate strings.  Currently I'm using `\\(["\\])` to
match backslash escapes, but I suspect it isn't enough.

/bpj

-- 
--

-- 
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

--- 
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe <at> googlegroups.com.
(Continue reading)

ping song | 15 Dec 00:57 2014
Picon

vim: search and jump

there is one feature that I had previously, but got lost after I
reinstall everything in a new machine from scratch - I couldn't
remember from which plugin this was provided...
anyway...the feature is this:

I search with /abc, if some matches found within current screen, the
cursor will move to the matched texts, but the text in current screen
won't move at all - it only move when the next match is beyond the
current screen.

see what I expected is this behavior:

this is my current screen texts:

----screen1 top-----------
1 abc
2 sldfsjsf alsjfdsl
3 12213 sdfjdksd abc
4 sfsdfsfdlfj
5 lsjfsfsaljf
6 lsjfdsfslfj
-----screen1 bottom-----

-----screen 2 top--------
7 sfsl abc lsjflsdflas
8
9
10
11
12
(Continue reading)

kamaraju kusumanchi | 13 Dec 07:21 2014
Picon

area selected by narrow region plugin remains highlighted

I normally hightlight a large function in a large c++ code using the
keyboard and do :NR.
Now, when I exit the new window using :q, I get back to the original
window I started from. However, in the original window, the selected
area is still highlighted in yellow.

This happens only some of the times and I am not able to figure out
why/when it happens. But when it does happen, the only way to get rid
of the yellow highlighting is to close that particular window and
reopen it.

The Narrow Region plugin (script version 32) is downloaded from
http://www.vim.org/scripts/script.php?script_id=3075 and I am using
gvim 7.2 on Redhat machines.

Does anyone else experience this issue? Any ideas on how to debug further?

By the way, this plugin is really awesome except for this minor issue.
Many thanks to Christian Brabandt for writing it.

raju

-- 
--

-- 
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

--- 
You received this message because you are subscribed to the Google Groups "vim_use" group.
(Continue reading)


Gmane