winpos doesn't seem to do anything

[GoogleCodeExporter]

What steps will reproduce the problem?

start MacVim and do

:winpos

Move the window and do it again.

What is the expected output? What do you see instead?

It's always at 0,0 and if you set it in .gvimrc, it doesn't affect where it 
shows up on the screen

What version of MacVim and OS X are you using (see "MacVim->About MacVim" and  
"Apple 
Menu->About This Mac" menu items, e.g. "Snapshot 40, 10.5.6 Intel")?

[ MacVim -> About MacVim didn't work ]

:version output:
VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Aug 21 2008 12:51:59)
MacOS X (unix) version
Compiled by Bjorn Winckler <bjorn.winckler@gmail.com>
Huge version with MacVim GUI.  Features included (+) or not (-):
+arabic +autocmd -balloon_eval +browse ++builtin_terms +byte_offset +cindent 
+clientserver 
+clipboard +cmdline_compl
+cmdline_hist +cmdline_info +comments +cryptv +cscope +cursorshape 
+dialog_con_gui +diff 
+digraphs +dnd -ebcdic +emacs_tags +eval
 +ex_extra +extra_search +farsi +file_in_path +find_in_path +float +folding -footer +fork() 
+fullscreen -gettext -hangul_input
+iconv +insert_expand +jumplist +keymap +langmap +libcall +linebreak 
+lispindent +listcmds 
+localmap +menu +mksession
+modify_fname +mouse +mouseshape +mouse_dec -mouse_gpm -mouse_jsbterm 
+mouse_netterm -mouse_sysmouse +mouse_xterm +multi_byte
+multi_lang -mzscheme -netbeans_intg +odbeditor -osfiletype +path_extra -perl 
+postscript 
+printer +profile +python +quickfix
+reltime +rightleft +ruby +scrollbind +signs +smartindent -sniff +statusline 
-sun_workshop 
+syntax +tag_binary +tag_old_static
-tag_any_white -tcl +terminfo +termresponse +textobjects +title +toolbar 
+transparency 
+user_commands +vertsplit +virtualedit
+visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows 
+writebackup -X11 
-xfontset -xim -xsmp -xterm_clipboard
-xterm_save
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
      user exrc file: "$HOME/.exrc"
  system gvimrc file: "$VIM/gvimrc"
    user gvimrc file: "$HOME/.gvimrc"
    system menu file: "$VIMRUNTIME/menu.vim"
  fall-back for $VIM: "/Applications/Vim.app/Contents/Resources/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MACVIM -Wall 
-Wno-unknown-
pragmas -pipe -I. -Iproto -DMACOS_X_UNIX -no-
cpp-precomp -I/Developer/SDKs/MacOSX10.4u.sdk/Developer/Headers/FlatCarbon  -g 
-O -
isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch
i386 -arch ppc     -
I/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/Python.framework/Vers
ions/2
.3/include/python2.3  -I
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universa
l-
darwin9.0
Linking: gcc   -L. -arch ppc -arch i386  -L/usr/local/lib -isysroot 
/Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc -o Vim -f
ramework Cocoa -framework Carbon      -lncurses  -liconv    -framework Python  
-lruby -lm

Please provide any additional information below.

Original issue reported on code.google.com by davetron...@gmail.com on 6 May 2009 at 3:54

[GoogleCodeExporter]

I am aware of this -- changing the window position from Vim is not yet 
supported.

Part of the reason I have not implemented it yet is that I don't understand 
what its use is.  Can you please tell me 
why you want this feature?

Original comment by bjorn.winckler@gmail.com on 6 May 2009 at 4:32

[GoogleCodeExporter]

With the old non-MacVim version of gvim that runs on OS X it would work (though 
was somewhat buggy), and 
I'd use it to place gvim windows at the same spot on the screen every time.  
I'd agree this is probably not a 
heavily used feature, but I didn't see an issue for it.

Original comment by davetron...@gmail.com on 6 May 2009 at 4:42

[GoogleCodeExporter]

I used it a few times to get an offscreen window back on screen. Hasn't be 
necessary with MacVim for quite a 
while, but I keep wishing this was supported perhaps once a year. Might be a 
good "first bug" for someone who 
wants to get started contributing?

Original comment by nicotha...@gmail.com on 7 May 2009 at 4:48

[GoogleCodeExporter]

I've finally fixed this problem (to be included in snapshot 52).

Original comment by bjorn.winckler@gmail.com on 1 Mar 2010 at 7:23

• Changed state: Fixed