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 window to the front
of the Z-order where it can be interacted with directly, not that it
is merely restored to 'normal' size.

-- 
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 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 existing
Vim window whether it's on the current desktop or a different one, and
whether the window was minimized or not:

wmctrl -xa gvim.Gvim

Because of the -x it matches the window to raise by it's window class,
which means any single Vim window could be raised by the command. In
your case that probably wouldn't be very useful, because you intended
to use remote_foreground(). However wmctrl can also match windows by
their id and title string.

Hope this helps.

 - Peter Odding

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


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 listmailed-bygooglegroups.com
hide details 3:50 PM (19 hours ago)
Hello

We have received your request to unsubscribe from vim_dev. In order for us
to complete the request, please reply to this email or visit the following
confirmation URL:

http://groups.google.com/group/vim_dev/subscribe?hl=en

If you have questions related to this or any other Google group, visit the
Help Center at http://groups.google.com/support/?hl=en.

Thanks,

google groups

On Wed, Dec 16, 2009 at 11:09 PM, John Beckett johnb.beck...@gmail.comwrote:

 Steven Sajous wrote:
  does anyone know why the unsubscribe does not work on this
  list? I have done it 4 times and got a confirmation every
  time. Still getting emails.

 Please say exactly what you did. You emailed what address
 approximately how many hours ago?

 John

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




-- 
A conservative is a liberal who has been mugged.  A liberal is a
conservative who has been hugged.

-- 
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 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 be able to do
some dcop magic instead, there's no reason you couldn't use wmctrl.

~Matt

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


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 histadd(search, for)'\
 -c 'call histadd(search, some)'   \
 -c 'call histadd(search, words)'  \
 -c 'call feedkeys(q/)'
 
 Problem with searching with *:
 
 vim -i NONE -c 'normal ido'\
 -c 'normal osome'  \
   -c 'normal osearching' \
   -c 'normal oplease'\
   -c 'normal gg' \
   -c 'normal *'  \
   -c 'call feedkeys(q/)'
 
 Note that the window containing the history is empty, although it should
 contain 4 elements in the first case and 1 element in the second case.

Thanks, I'll put it in the todo list.

-- 
Seen it all, done it all, can't remember most of it.

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\download, build and distribute -- http://www.A-A-P.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

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


[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 'call feedkeys(2G$gR\C-Y\C-Y)' \
  file.txt

where file.txt is:
#v+
abcdefghijklmnopqrstuvwxyz
 1 2 3 4 5
#v-

The result should be:
#v+
abcdefghijklmnopqrstuvwxyz
 1 2 3 4 z
#v-

but it is:
#v+
abcdefghijklmnopqrstuvwxyz
1 2 3 4 z1 2 3 4 5
#v-


The problem is caused by 0 passed to in_cinkeys() as the typed key.
Function in_cinkeys() is then unable to recognise the not found return
value from get_special_key_code().

The attached patch fixes the problem.

-- 
Cheers,
Lech

-- 
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.phpdiff --git a/src/edit.c b/src/edit.c
index 19e5b8d..2c5cc48 100644
--- a/src/edit.c
+++ b/src/edit.c
@@ -1419,7 +1419,7 @@ normalchar:
 	inserted_space = FALSE;
 
 #ifdef FEAT_CINDENT
-	if (can_cindent  cindent_on()
+	if (c != NUL  can_cindent  cindent_on()
 # ifdef FEAT_INS_EXPAND
 		 ctrl_x_mode == 0
 # endif
@@ -7397,6 +7397,11 @@ in_cinkeys(keytyped, when, line_is_empty)
 int		icase;
 int		i;
 
+if (NUL == keytyped)
+{
+	EMSG2(_(e_intern2), in_cinkeys());
+	return FALSE;
+}
 #ifdef FEAT_EVAL
 if (*curbuf-b_p_inde != NUL)
 	look = curbuf-b_p_indk;	/* 'indentexpr' set: use 'indentkeys' */


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.

 --
 Best Regards.

 Cornelius ( Yo-An Lin )
 E-mail: cornelius.h...@gmail.comhttp://c9s.blogspot.com/

  vim-syntax.patch
 1KViewDownload

  test.vim
  1KViewDownload

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