Re: Bug: Vim NSIS installer ignores the /D option for the target directory

On Sunday, September 14, 2014 5:13:38 AM UTC+2, Andrei Olsen wrote: > On Saturday, September 13, 2014 3:50:40 PM UTC+2, Tim Lebedkov wrote: > > Hello, > > > > the following command does not work as expected and installs Vim in > > C:\Program Files (x86)\vim\vim74: > > > > "%setup%" /S /D=%CD% >

Re: Bug: Vim NSIS installer ignores the /D option for the target directory

On Saturday, September 13, 2014 3:50:40 PM UTC+2, Tim Lebedkov wrote: > Hello, > > the following command does not work as expected and installs Vim in > C:\Program Files (x86)\vim\vim74: > > "%setup%" /S /D=%CD% > > -- /D= sets $InstDir before .onInit script code is called, so it doesn't work

Re: Can't paste into new windows when clipboard is set to unnamedplus

On 13/09/14 05:13 PM, Christian Brabandt wrote: On Sa, 13 Sep 2014, Bram Moolenaar wrote: Not really. Perhaps end_global_changes() clears the clipboard in a specific sequence of events? There might be a race condition, causing it to work when running in gdb. Or with/without using the opti

Re: Can't paste into new windows when clipboard is set to unnamedplus

On Sa, 13 Sep 2014, Bram Moolenaar wrote: > Not really. Perhaps end_global_changes() clears the clipboard in a > specific sequence of events? There might be a race condition, causing > it to work when running in gdb. Or with/without using the optimizer? Oh why, didn't I see this? I feel so st

[patch] clean up C/C++ string and character literal highlighting

A few bugs with C and C++ syntax highlighting: 1. In C mode, if c_no_c11 is set, then the highlighting of u8"foo" depends on c_no_cformat. If c_no_cformat is on, it gets highlighted even though u8"foo" is not a valid string literal pre-C11. 2. In C++ mode, if c_no_c11 is set, then (u8"foo") doe

Re: BufEnter and empty &buftype with cmdline-window (which shouldn't get triggered)

Oh, what a nasty bug! After having debugged eclim to find out what might trigger this it comes down to be reproducible like this: 1. Start vim: vim -u NONE -N --cmd 'call gettabvar(1, "bar") | au BufEnter * echom "TRIGGERED"' 2. Remove the initial message, e.g. ":" 3. Open the cmdline-window: q

Re: BufEnter and empty &buftype with cmdline-window (which shouldn't get triggered)

I could not reproduce this using `vim -u NONE -N`. TEST CASE: au BufEnter * echom "buftype:".&buftype.":" I've tracked it down to the eclim plugin, which is doing `silent doautocmd BufEnter` at least somewhere in its code, and causes this. Regards, Daniel. Am Samstag, 13. September 2014 19:49

BufEnter and empty &buftype with cmdline-window (which shouldn't get triggered)

It appears that &buftype is not correctly set with the BufEnter autocommand for a cmdline-window. I've noticed this with a BufEnter autocommand that checks for &buftype, and the documentation states that it should be "nofile" for the cmdline-window, but it's empty. Additionally, according to t

Re: Can't paste into new windows when clipboard is set to unnamedplus

Le samedi 13 septembre 2014 09:49:22 UTC-4, Jason Pleau a écrit : > Le samedi 13 septembre 2014 08:23:26 UTC-4, Christian Brabandt a écrit : > > > On Fr, 12 Sep 2014, Jason Pleau wrote: > > > > > > > > > > > > > Le jeudi 11 septembre 2014 14:23:46 UTC-4, Christian Brabandt a écrit: > > >

Re: How are we going to deal with C++14 features in syntax highlighting?

Brian Bi wrote: > cpp.vim has a lot of if statements like this: > > if !exists("cpp_no_cpp11") ... endif > > for C++11-only features. C++14 adds binary literals and digit > separators and I'm interested in adding these to cpp.vim. In analogy, > should I just wrap them in > > if !exists("cpp_no

Re: Can't paste into new windows when clipboard is set to unnamedplus

Christian Brabandt wrote: > On Fr, 12 Sep 2014, Jason Pleau wrote: > > > Le jeudi 11 septembre 2014 14:23:46 UTC-4, Christian Brabandt a écrit: > > > Interesting. I can reproduce the issue. I can't see how patch > > > 7.4.396 can cause this. However I noticed a couple of things: > > > > > > vim

Bug: Vim NSIS installer ignores the /D option for the target directory

Hello, the following command does not work as expected and installs Vim in C:\Program Files (x86)\vim\vim74: "%setup%" /S /D=%CD% -- -- -- 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 h

Re: Can't paste into new windows when clipboard is set to unnamedplus

Le samedi 13 septembre 2014 08:23:26 UTC-4, Christian Brabandt a écrit : > On Fr, 12 Sep 2014, Jason Pleau wrote: > > > > > Le jeudi 11 septembre 2014 14:23:46 UTC-4, Christian Brabandt a écrit: > > > > Interesting. I can reproduce the issue. I can't see how patch > > > > 7.4.396 can cause thi

Re: Issue 257 in vim: With clipboard=unnamed/plus, netrw plugin clears system PRIMARY/CLIPBOARD when vim is opened.

Comment #1 on issue 257 by chrisbr...@googlemail.com: With clipboard=unnamed/plus, netrw plugin clears system PRIMARY/CLIPBOARD when vim is opened. https://code.google.com/p/vim/issues/detail?id=257 This is currently discussed on the vim_dev mailinglist. See the thread starting here: ht

Re: Can't paste into new windows when clipboard is set to unnamedplus

On Fr, 12 Sep 2014, Jason Pleau wrote: > Le jeudi 11 septembre 2014 14:23:46 UTC-4, Christian Brabandt a écrit: > > Interesting. I can reproduce the issue. I can't see how patch > > 7.4.396 can cause this. However I noticed a couple of things: > > > > vim -u <(echo set clipboard=unnamedplus) -N

Issue 257 in vim: With clipboard=unnamed/plus, netrw plugin clears system PRIMARY/CLIPBOARD when vim is opened.

Status: New Owner: Labels: Type-Defect Priority-Medium New issue 257 by paoe...@gmail.com: With clipboard=unnamed/plus, netrw plugin clears system PRIMARY/CLIPBOARD when vim is opened. https://code.google.com/p/vim/issues/detail?id=257 What steps will reproduce the problem? 1. Set clipbo