On Sun, Feb 2, 2014 at 9:06 PM, Marcin Szamotulski <[email protected]> wrote:
> On 15:24 Sun 02 Feb , glts wrote:
>> On Sun, Feb 2, 2014 at 2:46 PM, Marcin Szamotulski <[email protected]> wrote:
>> > Is this supposed to work (note the ":" at the beginning):
>> > :/pattern
>> >
>> > This does not land on the pattern when matching on a longer line.
>> > For example the previous line in this email has only one place that
>> > matches \<a\>. If I run :/\<a\> when the cursor is on that line it will
>> > not land where I would expect. I don't know what is the pattern in this
>> > bug but some times it lands where it should.
>>
>> in
>>
>> :/pattern
>>
>> you are using /pattern as an Ex command range. It brings you to the next
>> line that contains pattern, just like
>>
>> :45
>> :'t
>>
>> bring you to line 45 and the line with mark t, respectively: :h 10.3.
>>
>> A suggestion: ask on vim_use about things that surprise you in Vim. It
>> happens quite often that people post here with an alleged bug only to be
>> told it's a feature.
>
> Yes, I use searches in range and this still is unexpected. Actually if
> vim would correctly set the column position this wouldn't be so
> surprising and still it would work fine for command range. What
> I want to report is that :/pattern doesn't land on the right column - it
> actually preserves the column.
Presumably this is because you have nostartofline set in your vimrc.
When reporting a bug, it's best to first try to reproduce it with
vim -Nu NONE
But again, this is a discussion that is better suited for vim_use.
Best,
--
David
--
--
You received this message from the "vim_dev" 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_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
