On 2011-06-09, Matt Mower wrote:
> Hi.
>
> I'm using MacVim Snapshot 57 but I've had this confirmed with another non-Mac
> user.
>
> In my .vimrc file I have
>
> set relativenumber
>
> and that works for files that I open from the command line.
>
> But it does not appear to work from files that I open from within Vim itself,
> using either :e <file>, NERDTree, or PeepOpen (a Cocoa based plugin).
>
> If I open a file from the command line relativenumber is turned on:
>
> verbose set number? => "nonumber, last set from ~/.vimrc"
> verbose set relativenumber? => "relativenumber, last set from ~/.vimrc"
>
> However, if I use ":new" relativenumber is not working despite my
> configuration.
By "not working" do you mean that you see only absolute line numbers
or no line numbers at all?
>
> verbose set number? => "number"
> verbose set relativenumber? => "relativenumber"
>
> So, in the latter case, it seems to think that both number and relativenumber
> are on when only number is on and it doesn't seem to know where they were set
> from.
Not knowing where they were set from seems to be normal behavior for
all options in a ":new" window, although it is not what I would
expect, either.
>
> Files opened using NERDTree and PeepOpen display the same behaviour.
>
> Is this a bug?
I don't know. I'm not seeing the problem myself, but I don't use
those plugins. What version of Vim are you using? It would also
help if you could reproduce this without any plugins, say exactly
what you do and exactly what you observe. For example, if I start
vim as
$ vim -N -u NONE --cmd 'set relativenumber'
:new
ahello
world<Esc>
I see in the old window
0
and in the new window
1 hello
0 world
Regards,
Gary
--
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
