Tomas Sandven | 25 Apr 21:42 2015
Picon

Feature request: Add a --role= command line argument for gvim

When multiple separate gvim instances are running, there is no good
way to tell them apart (that I've found.)

I suggest adding a command line argument so that gvim instances can be launched
with different X roles:

    gvim --role=notepad
    gvim --role=dev_proj1
    gvim --role=dev_proj2

This makes is easy to apply different window management rules to the
different gvim instances.

I am using i3wm with saved layouts to start my work environment. This
involves 8 terminals and 3 instances of gvim. gnome-terminal has a
--role= option, but gvim doesn't, so I currently have to position those windows
manually every time.

-- 
--

-- 
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

--- 
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscribe <at> googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jakson Alves de Aquino | 25 Apr 17:16 2015
Picon

E94 generated by bufwinnr()

Hi,

With the following in my vimrc

set debug=msg,throw

the function bufwinnr() generates E94 if the buffer does not
exist. Example:

:echo bufwinnr("nothing")

Is it correct to raise an error in this case? I think that there
should be no error because when the buffer does not exist the
function returns a predefined value (-1) that can be checked in
scripts.

Thanks!

-- 
Jakson Alves de Aquino
www.lepem.ufc.br/aquino.php?lang=en

-- 
--

-- 
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

--- 
You received this message because you are subscribed to the Google Groups "vim_dev" group.
(Continue reading)

zdm | 25 Apr 12:24 2015
Picon

How to link libwinpthread statically using mingw-w64-builds undef windows

Hi.

Can anybody help to build gvim with statically linked libwinpthread?

I use following command:

mingw32-make.exe -j%NUMBER_OF_PROCESSORS% -f Make_ming.mak ^
    STATIC_STDCPLUS=yes ^
    ARCH=x86-64 ^
    OPTIMIZE=MAXSPEED ^
    DIRECTX=yes ^
    FEATURES=HUGE ^
    OLE=yes ^
    POSTSCRIPT=yes ^
    gvim.exe xxd/xxd.exe vimrun.exe

but libwinpthread still linked dynamically.

gcc version 4.9.2.

Thanks.

-- 
--

-- 
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

--- 
You received this message because you are subscribed to the Google Groups "vim_dev" group.
(Continue reading)

Petr Vorel | 25 Apr 00:28 2015
Picon

kconfig.vim: support for matchit

Hi there,

here is a patch adding support for matchit plugin in kconfig.vim. Could you
please apply it to the source tree?

Thanks a lot!

Kind regards,
Petr

-- 
--

-- 
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

--- 
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscribe <at> googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
vim | 24 Apr 16:10 2015

Issue 356 in vim: match Error in tabs

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 356 by david2... <at> gmail.com: match Error in tabs
https://code.google.com/p/vim/issues/detail?id=356

What steps will reproduce the problem?
1. $ cat .vimrc #minimal vimrc
hi Error ctermfg=Red guifg=Red
syntax on
match ERROR /\s\+$/

2. $ vim -p foo bar
3. :tabn #go in tab 'bar'
4. Type anything with trailing whitespaces.

What is the expected output? What do you see instead?
Trailing whitespaces should be shown in red as it does for tab 'foo'.

What version of the product are you using? On what operating system?
Tried on different versions and platforms:
- Vim 7.3, Ubuntu 12.04
- Vim 7.3, Mac 10.9.5
- Vim 7.4 (snapshot 73 https://github.com/b4winckler/macvim/releases), Mac  
10.9.5

--

-- 
You received this message because this project is configured to send all  
issue notifications to this address.
(Continue reading)

Christian Brabandt | 23 Apr 21:17 2015

[patch] more non-breaking spaces

Bram,
Vim is treating U+0160 special with the listchars flag "nbsp".
But there are more non-breaking spaces, e.g. U+202F (narrow no-break 
space) and U+FEFF (zero width no-break space).

So here is a patch, that will also use the nbsp flag for those two chars 
as well.

Also, one could argue, U+FEFF should be displayed as ' ' and not as 
<feff> but for now I leave it as is.

Best,
Christian
-- 
Statt sich beim Humoristen über seine Gottlosigkeit sollten sich
manche lieber bei Gott über ihre Humorlosigkeit beklagen.
		-- Hans-Hermann Kesten

-- 
--

-- 
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

--- 
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscribe <at> googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Attachment (nbsp.diff): text/x-diff, 3178 bytes
(Continue reading)

Olaf Dabrunz | 20 Apr 08:22 2015

[patch] 'list += list' changes locked/RO list; issues changing v:oldfiles

Example:

    :let l = ['a', 'b', 3]
    :lockvar 1 l
    :let l += ['x']
        E741: Value is locked: l
    :let l
        l                     ['a', 'b', 3, 'x']

When the error message is shown, the list has already been changed.

Changing lists in the v: scope has a related problem: v:oldfiles is not
locked nor readonly and thus modifiable (as documented in
':he v:oldfiles'), but changing such a v: scope list variable prints an
error message and does not succeed, except when extending it with '+=':

    :let v:oldfiles += ['test']
        E685: Internal error: set_var()
    :let v:oldfiles
        v:oldfiles            ['fileA', 'fileB', ..., 'test']

    :let v:oldfiles = ['otherfile']
        E685: Internal error: set_var()
    :let v:oldfiles
        v:oldfiles            ['fileA', 'fileB', ..., 'test']

The patch adds checks for the lock and readonly flags of a variable
before preparing a [+-.]= assignment, as that preparation alone is
sufficient to extend an existing list variable. (Preparations for other
variable types do not change existing variables.)
(Continue reading)

vim | 23 Apr 15:06 2015

Issue 355 in vim: :swapname prints different string at different occasions

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 355 by istjanic... <at> gmail.com: :swapname prints different string  
at different occasions
https://code.google.com/p/vim/issues/detail?id=355

What steps will reproduce the problem?

1. % vim -u NONE -U NONE --noplugin
2. :edit a_file.txt
3. :swapname           -> prints ".a_file.txt.swp"
4. :q!
5. % vim -u NONE -U NONE --noplugin a_file.txt
6. :swapname           -> prints "/home/user/.a_file.txt.swp"

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

Prints the path of the swapfile as relative or absolute path, depending on  
when I called the command. Since I use the output in a script, it would be  
nice if the output would be consistent.

What version of the product are you using? On what operating system?

Both Vim 7.2 and Vim 7.4 on Linux.

--

-- 
You received this message because this project is configured to send all  
issue notifications to this address.
(Continue reading)

Daniel Hahler | 23 Apr 12:56 2015
Picon

Moving to Github: use github.com/vim-jp/vim as base

Hi,

in the process of moving the repository to Github I suggest using the existing mirror from
https://github.com/vim-jp/vim as a starting point.

This would make it easier for existing patches / pull requests (based on this AFAIK most popular Git mirror)
to get integrated into Vim itself later, because of the then common history.

Additionally it would make it easier/trivial for users that are using this mirror to migrate to Vim's new repository.

Regards,
Daniel.

-- 
--

-- 
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

--- 
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscribe <at> googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Bram Moolenaar | 22 Apr 22:18 2015
Picon
Picon

Patch 7.4.712


Patch 7.4.712 (after 7.4.710)
Problem:    Missing change in another file.
Solution:   Also change message.c
Files:      src/message.c

*** ../vim-7.4.711/src/message.c	2014-12-17 14:36:10.363090985 +0100
--- src/message.c	2015-04-21 18:21:13.146538823 +0200
***************
*** 1761,1766 ****
--- 1761,1771 ----
  		c = lcs_trail;
  		attr = hl_attr(HLF_8);
  	    }
+ 	    else if (c == ' ' && list && lcs_space != NUL)
+ 	    {
+ 		c = lcs_space;
+ 		attr = hl_attr(HLF_8);
+ 	    }
  	}

  	if (c == NUL)
*** ../vim-7.4.711/src/version.c	2015-04-21 19:10:41.315067887 +0200
--- src/version.c	2015-04-22 22:15:55.173135367 +0200
***************
*** 743,744 ****
--- 743,746 ----
  {   /* Add new patch number below this line */
+ /**/
+     712,
(Continue reading)

Paul Moore | 22 Apr 21:03 2015
Picon

Building Vim with Visual Studio 2015

Has anyone tried building Vim with Visual C 2015 on Windows yet? I wanted to try building a copy of Vim with
Python 3.5 enabled, just to see how well it worked - Python 3.5 uses VC 2015 to build, so I wanted to use the
same version for Vim to avoid any weird C runtime clashes that might occur. And just for the interest :-)

There seem to be a number of issues:

1. Win32.mak is no longer available. I see that I can set SDK_INCLUDE_DIR to point to a version of it, but that
means installing an old SDK or an old version of Visual Studio, so it's less than ideal...

2. The use of /nodefaultlib causes a load of "unresolved external symbol malloc" and similar issues. The C
runtime has been reorganised in VC 2015, which maybe is why this is having issues.

Has anyone else tried to build with VC2015, and if so have you worked out how to fix these issues in a
reasonable way? Just removing the use of /nodefaultlib *seems* to work, so I could use that for now, but I
don't know if that could have problems that I haven't spotted.

Thanks,
Paul

-- 
--

-- 
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

--- 
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscribe <at> googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
(Continue reading)


Gmane