Hi,
2015-12-4(Fri) 14:48:23 UTC+9 h_east:
> Hi Paolo,
>
> 2015-12-4(Fri) 13:55:27 UTC+9 Paolo Bolzoni:
> > Dear list,
> >
> > I use vim to write C++ code and often I start the program using a
> > command line like
> > $ vcpp classX.*
> > (vcpp is an alias for vim -u ~/.vim/vcpp/vimrc where the C
On 2015-12-04, Paolo Bolzoni wrote:
> Dear list,
>
> I use vim to write C++ code and often I start the program using a
> command line like
> $ vcpp classX.*
> (vcpp is an alias for vim -u ~/.vim/vcpp/vimrc where the C++ settings are)
>
> So vim opens the files with definitions and headers. Howeve
Hi Paolo,
2015-12-4(Fri) 13:55:27 UTC+9 Paolo Bolzoni:
> Dear list,
>
> I use vim to write C++ code and often I start the program using a
> command line like
> $ vcpp classX.*
> (vcpp is an alias for vim -u ~/.vim/vcpp/vimrc where the C++ settings are)
>
> So vim opens the files with definitions
This is expected. Your complaint seems to stem from a confusion
between "line separators" (the DOS and Windows concept) and "line
endings" (the Unix and Vim concept). Let us explain how Vim does it:
Vim doesn't store the individual lines differently based on whether
they had an end-of-line in the
Dear list,
I use vim to write C++ code and often I start the program using a
command line like
$ vcpp classX.*
(vcpp is an alias for vim -u ~/.vim/vcpp/vimrc where the C++ settings are)
So vim opens the files with definitions and headers. However if the
file is compiled vim also opens the .o file
On 2015-12-03, alessio.poll...@gmail.com wrote:
> Hi, today I discovered a strange issue that lead me to waste 2
> hours of time, since I rely on vim but it seems I discovered a
> bug.
>
> When working with files I usually put on end of line markers
> with the command : set list . Today I had a fil
Hi, today I discovered a strange issue that lead me to waste 2 hours of time,
since I rely on vim but it seems I discovered a bug.
When working with files I usually put on end of line markers with the command :
set list .
Today I had a file with the last line without a LF character but though I
On 2015-12-03, Charles E Campbell wrote:
> Try Rainbow.vim from my website:
> http://www.drchip.org/astronaut/vim/index.html#RAINBOW . It currently
> handles c, c++, matlab, Latex, javascript, and vim.
I just did that, following the link above, but ~/.vim/Rainbow.vba.gz
does not contain a rainbo
Eric Christopherson wrote:
> On Wed, Aug 26, 2015, Fabian Nick wrote:
>> Hi all,
>>
>> ss there a way to highlight if-else-endif structures in Vim on demand based
>> on their 'level' in the overall program hierarchy? I.e. I want something like
>>
>> if <<< highlight in red
>>foo
>> else r
On 1 Dec 2015, at 21:31, Christian Brabandt wrote:
> Attached is a patch.
Thanks!
I applied the patch to MacVim 7.4.947 and I can confirm it solved both problems
for me.
Thanks again,
Yours,
Andrew
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your rep
> On Di, 01 Dez 2015, b...@airbladesoftware.com wrote:
> > Hello!
> >
> > Under certain circumstances the colorcolumn becomes misaligned by one
> > character:
> >
> > 1. A lign has a sign whose text is a fullwidth character.
> > 2. The colorcolumn is a column after the end of the text on the li
11 matches
Mail list logo