Re: set default fileformat with empty first buffer

On Sun, Mar 20, 2016 at 08:46:23AM +, Mike Williams wrote: > I noticed a problem with the fileformats option not being applied to the > initial buffer when VIM is started without any initial buffer content. I > mainly work on Windows and have fileformats=unix,dos so the default file > format

Patch 7.4.1633

Patch 7.4.1633 Problem:If the help tags file was removed "make install" fails. (Tony Mechelynck) Solution: Only try moving the file if it exists. Files: src/Makefile *** ../vim-7.4.1632/src/Makefile2016-03-21 22:38:30.53968 +0100 --- src/Makefile

Patch 7.4.1634

Patch 7.4.1634 Problem:Vertical movement after CTRL-A ends up in the wrong column. (Urtica Dioica) Solution: Set curswant when appropriate. (Hirohito Higashi) Files: src/ops.c, src/testdir/test_increment.vim *** ../vim-7.4.1633/src/ops.c 2016-03-05 17:25:34.791256346

Re: Patch 7.4.1087

Hirohito Higashi wrote: > Hi Urtica, > > 2016-3-21(Mon) 6:33:45 UTC+9 Urtica dioica: > > 7.4.1087 caused a regression (still present in 7.4.1627). > > > > hello 1 > > world > > --- ljx > > hello 2 > > wrld > > > > Using j or k after a regular increment/decrement that moves the cursor > >

Patch 7.4.1630

Patch 7.4.1630 Problem:Unicode table for double width is outdated. Solution: Update to the latest Unicode standard. Files: src/mbyte.c *** ../vim-7.4.1629/src/mbyte.c 2016-03-21 22:09:39.556789855 +0100 --- src/mbyte.c 2016-03-21 22:13:43.090235367 +0100 *** *** 1252,1257

Re: first window blank if opening encrypted file

Toothpik wrote: > I've got a module in which I keep passwords, encrypted with blowfish2 -- > recently (and I can't be more specific than that) when I open that file > it opens a completely blank gvim window, where there used to be a > message informing me that the module is encrypted and I need

Re: Build problems after adding patches 7.4.1616 to 7.4.1626 (plus one runtime files update)

Tony Mechelynck wrote: > Build problems after adding patches 7.4.1616 to 7.4.1626 (plus one > runtime files update) > > 1. Warning in channel.c (in Huge only since this file is not compiled for > Tiny): > > gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread > -I/usr/include/gtk-2.0

Patch 7.4.1631

Patch 7.4.1631 Problem:Compiler doesn't understand switch on all enum values. (Tony Mechelynck) Solution: Initialize variable. Files: src/channel.c *** ../vim-7.4.1630/src/channel.c 2016-03-21 12:36:24.598191820 +0100 --- src/channel.c 2016-03-21

Patch 7.4.1632

Patch 7.4.1632 Problem:List of test targets is outdated. Solution: Update to current list of test targets. Files: src/Makefile *** ../vim-7.4.1631/src/Makefile2016-03-13 14:34:07.628766258 +0100 --- src/Makefile2016-03-21 22:36:40.439811969 +0100 *** ***

Patch 7.4.1635

Patch 7.4.1635 Problem:Channel test is a bit flaky. Solution: Remove 'DETACH' if it's there. Files: src/test_channel.vim *** ../vim-7.4.1634/src/testdir/test_channel.vim2016-03-20 22:16:52.660922719 +0100 --- src/testdir/test_channel.vim2016-03-21 23:12:26.513356568

Re: Patch 7.4.1604 - Introduced invalid argument

Yasuhiro Matsumoto wrote: > > > On Sunday, March 20, 2016 at 11:14:50 PM UTC+9, Elimar Riesebieter wrote: > > > > * Bram Moolenaar [2016-03-19 18:42 +0100]: > > > > > > > > > > > > > > Patch 7.4.1604 > > > > > Problem:Although emoji characters are ambiguous width, best

Re: Arrow characters shouldn't be wide

Ben Fritz wrote: > A recent patch (since 1507; I assume it was 1604) broke my preferred > "showbreak" setting for text files. > > I have been setting showbreak to ↖ (U+2196 NORTH WEST ARROW). The > glyph for this character still only occupies a single cell on my gvim, > however it is treated as

Re: Problems compiling vim

Hi Niels, 2016-3-20(Sun) 23:18:30 UTC+9 Niels Kobschätzki: > Hi, > > I am trying to compile vim on Fedora 23. Tbh I am not a developer and > don't have a lot of knowledge about make-files etc but I want some > features that the pre-compiled binaries for Fedora don't deliver. > When I compile

Re: Patch - Filtering entries in the quickfix/location list

Hi Gary, On Sun, Mar 20, 2016 at 10:32 PM, Gary Johnson wrote: > On 2016-03-13, Yegappan Lakshmanan wrote: >> Hi Bram, >> >> On Sun, Mar 13, 2016 at 11:44 AM, Bram Moolenaar wrote: >> > >> > Yegappan Lakshmanan wrote: >> > >> >> >> I am attaching a patch to add the

Patch 7.4.1628

Patch 7.4.1628 Problem:64-bit Compiler warning. Solution: Change type of variable. (Mike Williams) Files: src/channel.c *** ../vim-7.4.1627/src/channel.c 2016-03-20 20:56:56.036283020 +0100 --- src/channel.c 2016-03-21 12:34:39.055256519 +0100 *** ***

Re: Patch 7.4.1604 - Introduced invalid argument

On Monday, March 21, 2016 at 1:54:08 AM UTC+9, Bram Moolenaar wrote: > Yasuhiro Matsumoto wrote: > > > On Sunday, March 20, 2016 at 11:14:50 PM UTC+9, Elimar Riesebieter wrote: > > > * Bram Moolenaar [2016-03-19 18:42 +0100]: > > > > > > > > > > > Patch 7.4.1604 > > > >

[bug] another use of free memory in quickfix code

Hi afl-fuzz found another crash with use of freed memory in vim-7.4.1627 (and older) in quickfix code. This is a different bug that the one fixed recently in Vim-7.4.1592: $ cat > crash.vim

Re: set default fileformat with empty first buffer

On 21/03/2016 06:39, Marius Gedminas wrote: On Sun, Mar 20, 2016 at 08:46:23AM +, Mike Williams wrote: I noticed a problem with the fileformats option not being applied to the initial buffer when VIM is started without any initial buffer content. I mainly work on Windows and have

Re: [vim] Vim cryptmethod uses SHA-256 for password-based key derivation (#639)

On Monday, March 21, 2016 at 11:04:15 AM UTC-5, Scott wrote: > (Slight nit: it's PBKDF2. The acronym stands for "Password-Based Key > Derivation Function #2".) > > Thanks, I knew that, I just was typing faster than I was thinking apparently. That's one of those acronyms I really need to

Re: Arrow characters shouldn't be wide

On Monday, March 21, 2016 at 11:40:14 AM UTC-5, Ben Fritz wrote: > On Monday, March 21, 2016 at 11:29:20 AM UTC-5, Ben Fritz wrote: > > A recent patch (since 1507; I assume it was 1604) broke my preferred > > "showbreak" setting for text files. > > > > > More problems. I also have a plugin

Re: [vim] Vim cryptmethod uses SHA-256 for password-based key derivation (#639)

On Monday, March 21, 2016 at 11:00:31 AM UTC-5, Ben Fritz wrote: > On Saturday, March 19, 2016 at 1:43:30 PM UTC-5, Demetri Obenour wrote: > > Argon2 is implemented in libsodium and is the winner of the Password > > Hashing Competition. It is designed as a KDF. > > > > > > However, note that

Re: Arrow characters shouldn't be wide

On Monday, March 21, 2016 at 11:29:20 AM UTC-5, Ben Fritz wrote: > A recent patch (since 1507; I assume it was 1604) broke my preferred > "showbreak" setting for text files. > More problems. I also have a plugin (signify) which places characters of my choosing in the sign column for text

Arrow characters shouldn't be wide

A recent patch (since 1507; I assume it was 1604) broke my preferred "showbreak" setting for text files. I have been setting showbreak to ↖ (U+2196 NORTH WEST ARROW). The glyph for this character still only occupies a single cell on my gvim, however it is treated as a wide character so it uses

Re: [vim] Add GUI option 's' to prevent resizing when tab bar is shown, vert split happens,etc (#703)

On 2016-03-21, cvwillegen wrote: > In runtime/doc/options.txt: > > > @@ -3824,6 +3824,13 @@ A jump table for the options with a short > > description can be found at |Q_op|. > > removing it after the GUI has started has no effect. > >

Re: [vim] Vim cryptmethod uses SHA-256 for password-based key derivation (#639)

On Saturday, March 19, 2016 at 1:43:30 PM UTC-5, Demetri Obenour wrote: > Argon2 is implemented in libsodium and is the winner of the Password Hashing > Competition. It is designed as a KDF. > > > However, note that the rest of Vim's cryptmethod is also poorly implemented. > My suggestion is

Re: Arrow characters shouldn't be wide

On Mon, Mar 21, 2016 at 12:29 PM, Ben Fritz wrote: > A recent patch (since 1507; I assume it was 1604) broke my preferred > "showbreak" setting for text files. > > I have been setting showbreak to ↖ (U+2196 NORTH WEST ARROW). The glyph > for this character still only

Re: Patch 7.4.1087

> Attached patch would fix this issue. > Please confirm this patch. Works for me. Thanks very much. -- -- 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 ---

Re: Arrow characters shouldn't be wide

* Ben Fritz [2016-03-21 09:40 -0700]: > On Monday, March 21, 2016 at 11:29:20 AM UTC-5, Ben Fritz wrote: > > A recent patch (since 1507; I assume it was 1604) broke my preferred > > "showbreak" setting for text files. > > > > > More problems. I also have a plugin

Re: Arrow characters shouldn't be wide

On Monday, March 21, 2016 at 11:52:38 AM UTC-5, Manuel Ortega wrote: > > At least some of these worries can be fixed by setting "noemoji", but I find > it inexplicable that "emoji" is ON by default, given how it messes up > operating with non-emoji characters. > > > Either Vim needs to only

Re: Arrow characters shouldn't be wide

* Ben Fritz [2016-03-21 10:01 -0700]: > On Monday, March 21, 2016 at 11:52:38 AM UTC-5, Manuel Ortega wrote: > > > > At least some of these worries can be fixed by setting > > "noemoji", but I find it inexplicable that "emoji" is ON by > > default, given how it messes

Re: Problems compiling vim

On 16/03/21 06:20, h_east wrote: Hi Niels, 2016-3-20(Sun) 23:18:30 UTC+9 Niels Kobschätzki: Hi, I am trying to compile vim on Fedora 23. Tbh I am not a developer and don't have a lot of knowledge about make-files etc but I want some features that the pre-compiled binaries for Fedora don't

first window blank if opening encrypted file

I've got a module in which I keep passwords, encrypted with blowfish2 -- recently (and I can't be more specific than that) when I open that file it opens a completely blank gvim window, where there used to be a message informing me that the module is encrypted and I need to input the key thinking

Patch 7.4.1629

Patch 7.4.1629 Problem:Handling emoji characters as full width has problems with backwards compatibility. Solution: Remove ambiguous and double width characters from the emoji table. Use a separate table for the character class. (partly by Yasuhiro