remote_foreground() doesn't work exactly on GTK (on KDE)

2009-12-17 Fir de Conversatie ron
If the gvim server is minimized then using remote_foreground() does make it restore to its original size. However, whether it was minimized or not, if another window is above it in Z-order, the restored gvim will appear *behind* the front window. I would have thought that foreground begins the

Re: remote_foreground() doesn't work exactly on GTK (on KDE)

2009-12-17 Fir de Conversatie ron
Apparently it's a problem (==feature) with the way gtk_window_present () works. Window managers have the option of ignoring the restacking request. So is there are workaround? -- You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php

Re: remote_foreground() doesn't work exactly on GTK (on KDE)

2009-12-17 Fir de Conversatie Peter Odding
So is there are workaround? Not in Vim, but since you mention GTK the command-line program wmctrl might offer a workaround? I'm using it in a shell script that wraps /usr/bin/gvim to open files from the command-line and in the GUI within a single Gvim instance. The following command raises an

Re: [patch] Initialise history before adding elements

2009-12-17 Fir de Conversatie Steven Sajous
Last Attempt: fromvim_dev vim_dev+unsubconf...@googlegroups.comvim_dev%2bunsubconf...@googlegroups.com to dateWed, Dec 16, 2009 at 3:50 PMsubjectUnsubscribe request for vim_dev [{EJ2QpdkEk8REPI7uh0E0}]mailing listvim_dev.googlegroups.com Filter messages from this mailing

Re: remote_foreground() doesn't work exactly on GTK (on KDE)

2009-12-17 Fir de Conversatie Matt Wozniski
On Thu, Dec 17, 2009 at 10:59 AM, ron wrote: Hi, Peter - Thanks, that is a help.  I'm using KDE though, so maybe some DCOP incantation or similar would be what I need? wmctrl is window manager agnostic - its basic features should work in just about every window manager. So, while you might

Re: [patch] Initialise history before adding elements

2009-12-17 Fir de Conversatie Bram Moolenaar
Lech Lorens wrote: The attached patch fixes the behaviour of Vim where histadd() and searching with * fail to add elements to history if the history is empty. How to reproduce: Problem with histadd(): $ vim -i NONE -c 'call histadd(search, search)' \ -c 'call

[patch] C-Y in virtual replace when line above is shorter

2009-12-17 Fir de Conversatie Lech Lorens
Vim erroneously re-indents the current line if in virtual replace mode C-Y or C-E is pressed while the line above or below respectively is not long enough. To reproduce the problem execute: $ vim -u NONE -U NONE -i NONE -c 'set nocp noet ts=8 inde=0 indk=:' \ -c

Re: vim syntax file patch

2009-12-17 Fir de Conversatie c9s
any comment ? On Dec 15, 9:11 pm, Cornelius cornelius.h...@gmail.com wrote: Hi folks, I found that VimL syntax doesnt fold for something like: fun! g:Test() endf it folds for : fun! g:Test.ok() endf so this is a patch of fixing the global function folding and my test code. --