Gary, Tim,
Thank you for your suggestions. The %>8c trick works, and I also found another
way:
:%s;\v\./\zs;;
However:
Since I don't want to type this every time, I made a cnoremap like so:
cnoremap %s %s/\v\.\/\zs
Which works, but what about all other operations that you can do on a
Efraim Yawitz wrote:
> I just solved a minor issue which someone else may have as well, so here it
> is:
>
> I sometimes take the compiler output from Visual Studio and read it into
> Vim with a :cfile command so I can fix the errors in Vim. I have been using
>
> set
On 2018-12-03 11:27, Tim Chase wrote:
> On 2018-12-03 17:40, Magnus Woldrich wrote:
> > and I need vim to *think* that the buffer starts at column 9.
>
> :%s/\%>9c /_/g
Whoops, off by one. I misread that as "I want to protect through
column 9". So use "8" instead.
Amused that as I pushed
On 2018-12-03 17:40, Magnus Woldrich wrote:
> I'd like to stop vim from modifying the first n columns of a
> buffer, no matter what I do in it.
>
> Consider the following data, where the number isn't vims internal
> line numbers, but actual data:
>
>50 ./bin/
>51 ./cgi/
>52 ./dev/
>
On 2018-12-03, Magnus Woldrich wrote:
> Hi list,
>
> I'd like to stop vim from modifying the first n columns of a buffer, no
> matter what I do in it.
>
> Consider the following data, where the number isn't vims internal line
> numbers, but actual data:
>
> 50 ./bin/
> 51 ./cgi/
> 52
Hi list,
I'd like to stop vim from modifying the first n columns of a buffer, no
matter what I do in it.
Consider the following data, where the number isn't vims internal line
numbers, but actual data:
50 ./bin/
51 ./cgi/
52 ./dev/
53 ./devlaleh/
54 ./emu/
55 ./etc/
Now, I'd want
Hi,
I just solved a minor issue which someone else may have as well, so here it
is:
I sometimes take the compiler output from Visual Studio and read it into
Vim with a :cfile command so I can fix the errors in Vim. I have been using
set errorformat=%*[0-9]%*[>]\ %#%f(%l)\ :\ %m
which someone
