Friday, November 27, 2009

Re: Problem about the "browse" command

On 27/11/09 09:41, winterTTr wrote:
>
>
> On Fri, Nov 27, 2009 at 4:31 PM, Tony Mechelynck
> <antoine.mechelynck@gmail.com <mailto:antoine.mechelynck@gmail.com>> wrote:
>
> On 30/10/09 15:50, Ben Fritz wrote:
> >
> >
> >
> > On Oct 29, 8:49 pm, winterTTr<winterttr....@gmail.com
> <mailto:winterttr....@gmail.com>> wrote:
> >> There is a problem about the "browse" command for my gvim now.
> >> However, i can not find the reason for it.
> >>
> >> I remember that , when i run the command
> >> :browse w <filename>
> >> to a new buffer, there should be a dialog shown to let me select
> >> the file position for saving , but now the dialog does not show any
> >> more, it seems
> >> like that , i have never input the command . Nothing happens, and
> >> the command following the "browse" which is "w<filename>" for
> this case
> >> is not executed neither.
> >>
> >
> > I cannot reproduce, using the Vim 7.2.267 "Cream" build on
> Windows XP.
> > Does the same thing happen for you when running from the command
> > prompt with gvim -N -u NONE?
>
> Neither can I on Linux with gvim 7.2.309 for GTK2/Gnome2 GUI.
>
> WinterTTr, you _are_ giving a "real" filename aren't you, without the
> less-than and greater-than signs given in your message?
>
> When I do
> :browse w
> I see a save-as dialog with the directory and current filename filled-in
> as defaults, and when I do
> :browse w foobar
> the default filename is replaced by foobar
>
>
> I compile the new version ( 7.2.276 ) from svn not long ago, but the
> problem is
> also occurred now.
> I am using VIM on office WindowsXP and the same EXE file on Win7 home.
> However, the same things happen, and i can not see the FileBrowser
> Dialog anymore.
>
> It is really inconvenient, but i don't know how to fix it.
> Does this thing just happen to me ?

Well, have you tried, as Ben said, to start Vim from the command prompt as

gvim -N -u NONE

so that any "weird" settings in your vimrc don't make the waters murkier?

If this works, then it must be something in your vimrc or in a
nonstandard plugin. To know which, try either

gvim -N -u NORC

or

gvim --noplugin


Best regards,
Tony.
--
"But don't you worry, its for a cause -- feeding global corporations
paws."

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

No comments: