Re: make report fails in testdir at v7.4.2290

* Dominique Pellé <dominique.pe...@gmail.com> [2016-08-29 09:21 +0200]: > Elimar Riesebieter <riese...@lxtec.de> wrote: > > > $ make report > > > > Test results: > > > > > > From test_alot.vim: > > Found errors in Test

make report fails in testdir at v7.4.2290

$ make report Test results: >From test_alot.vim: Found errors in Test_tabpage_with_tab_modifier(): function RunTheTest[9]..Test_tabpage_with_tab_modifier[13]..40_check_tab line 4: Expected 'help' but got 'text' function RunTheTest[9]..Test_tabpage_with_tab_modifier[14]..40_check_tab line 4:

Re: Build 7.4.2243: Makefile:41: recipe for target 'report' failed

* Dominique Pellé <dominique.pe...@gmail.com> [2016-08-23 21:58 +0200]: > Elimar Riesebieter <riese...@lxtec.de> wrote: > > > * Dominique Pellé <dominique.pe...@gmail.com> [2016-08-23 14:53 +0200]: > > > > [...] > >> >> 2016-8-23(Tue) 19

Re: Build 7.4.2243: Makefile:41: recipe for target 'report' failed

* Dominique Pellé <dominique.pe...@gmail.com> [2016-08-23 14:53 +0200]: [...] > >> 2016-8-23(Tue) 19:15:31 UTC+9 Elimar Riesebieter: > > [...] > >> > I tried to build 7.4.2243 which failed with the above messages. So > >> > why do you want to k

Re: Build 7.4.2243: Makefile:41: recipe for target 'report' failed

* h_east <h.east@gmail.com> [2016-08-23 04:49 -0700]: > Hi Elimar, > > 2016-8-23(Tue) 19:15:31 UTC+9 Elimar Riesebieter: [...] > > I tried to build 7.4.2243 which failed with the above messages. So > > why do you want to know which version I am running? This

Re: Build 7.4.2243: Makefile:41: recipe for target 'report' failed

* h_east <h.east@gmail.com> [2016-08-23 02:36 -0700]: > Hi Elimar, > > 2016-8-23(Tue) 18:28:18 UTC+9 Elimar Riesebieter: > > Executed 162 tests¬ > > 1 FAILED:¬ > > From test_alot.vim: > > Found errors in Test_tabpage_with_tab_modifi

Build 7.4.2243: Makefile:41: recipe for target 'report' failed

Executed 162 tests¬ 1 FAILED:¬ From test_alot.vim: Found errors in Test_tabpage_with_tab_modifier():¬ function RunTheTest[9]..Test_tabpage_with_tab_modifier[13]..39_check_tab line 4: Expected 'help' but got 'text' Repeated 9 times. Elimar -- We all know Linux is great... it does

ftp.vim.org down?

ping ftp.vim.org PING ftp.vim.org(ftp.nluug.nl (2001:67c:6ec:221:145:220:21:40)) 56 data bytes --- ftp.vim.org ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2025ms -- You cannot propel yourself forward by patting yourself on the back. -- -- You received

conftest segfault on linux kernel

Hi all, while compiling vim I get errors in syslog on my linux kernels x86-64 (4.4, 4.5, 4.6): syslog.1:Apr 15 00:07:26 pipin kernel: conftest[12645]: segfault at 8bed6030 ip 55fa8a5b473e sp 7ffc6214adc0 error 5 in conftest[55fa8a5b4000+1000] syslog.1:Apr 15 00:07:26 pipin

Re: Vim 7.5 or Vim 8?

* Dominique Pellé [2016-04-05 09:27 +0200]: > Bram Moolenaar wrote: > > > I have been wondering if the next release should be called 7.5 or 8. > > We have quite a few new features, but not that many as with the Vim 7 > > release. Well, that was a

Re: [PATCH] Debian's package checker lintian lacks Keywords entry in desktop files.

* Bram Moolenaar [2016-04-02 15:22 +0200]: [...] > > Thanks. However, the colon should be an equal sign: > > +Keywords=Text;editor; This was correczed in the 2nd mail of this thread. Elimar -- Excellent day for drinking heavily. Spike the office water

Re: [PATCH] Debian's package checker lintian lacks Keywords entry in desktop files.

Should be = instead of: - runtime/gvim.desktop | 1 + runtime/vim.desktop | 1 + 2 files changed, 2 insertions(+) - diff --git a/runtime/gvim.desktop b/runtime/gvim.desktop index 24d7445..bcfc94d 100644 --- a/runtime/gvim.desktop +++ b/runtime/gvim.desktop @@ -74,6 +74,7 @@

[PATCH] Debian's package checker lintian lacks Keywords entry in desktop files.

runtime/gvim.desktop | 1 + runtime/vim.desktop | 1 + 2 files changed, 2 insertions(+) diff --git a/runtime/gvim.desktop b/runtime/gvim.desktop index 24d7445..bcfc94d 100644 --- a/runtime/gvim.desktop +++ b/runtime/gvim.desktop @@ -74,6 +74,7 @@ TryExec=gvim Exec=gvim -f %F Terminal=false

[PATCH] Debian's package checker lintian found a spell error in manpage

--- runtime/doc/vim.1 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/runtime/doc/vim.1 b/runtime/doc/vim.1 index e2dcd42..e3c8773 100644 --- a/runtime/doc/vim.1 +++ b/runtime/doc/vim.1 @@ -321,7 +321,7 @@ When N is omitted, open one tab page for each file. \-R Read-only

Re: Patch 7.4.1630

* Bram Moolenaar [2016-03-21 22:16 +0100]: > > Patch 7.4.1630 > Problem:Unicode table for double width is outdated. > Solution: Update to the latest Unicode standard. > Files: src/mbyte.c Now my setup runs without setting noemoji. Thanks! Elimar -- Learned

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: 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: Patch 7.4.1604 - Introduced invalid argument

* Bram Moolenaar <b...@moolenaar.net> [2016-03-20 17:53 +0100]: > > Yasuhiro Matsumoto wrote: > > > On Sunday, March 20, 2016 at 11:14:50 PM UTC+9, Elimar Riesebieter wrote: > > > * Bram Moolenaar <b...@moolenaar.net> [2016-03-19 18:42 +0100]: &g

Re: Patch 7.4.1604 - Introduced invalid argument

* mattn <mattn...@gmail.com> [2016-03-20 08:12 -0700]: > On Sunday, March 20, 2016 at 11:14:50 PM UTC+9, Elimar Riesebieter wrote: > > * Bram Moolenaar <b...@moolenaar.net> [2016-03-19 18:42 +0100]: > > > > > > > > Patch 7.4.1604 > > > Pro

Re: Patch 7.4.1604 - Introduced invalid argument

* Bram Moolenaar [2016-03-19 18:42 +0100]: > > Patch 7.4.1604 > Problem:Although emoji characters are ambiguous width, best is to treat > them as full width. > Solution: Update the Unicode character tables. Add the 'emoji' options. > (Yasuhiro

Re: Patch 7.4.1450

* Bram Moolenaar [2016-02-28 18:04 +0100]: > > Patch 7.4.1450 > Problem:Json encoding still fails when encoding is not utf-8. > Solution: Set 'encoding' before :scriptencoding. Run the json test > separately to avoid affecting other tests. > Files:

Re: Patch 7.4.1448

* Bram Moolenaar [2016-02-28 16:30 +0100]: > > Patch 7.4.1448 > Problem:JSON tests fail if 'encoding' is not utf-8. > Solution: Force encoding to utf-8. > Files: src/testdir/test_json.vim Hmm, this one fails with: Executed 33 tests 2 FAILED: Found errors in

Re: Patch 7.4.1446

* Bram Moolenaar [2016-02-28 15:21 +0100]: > > Patch 7.4.1446 > Problem:Crash when using json_decode(). > Solution: Terminate string with a NUL byte. > Files: src/json.c Building this with LC_ALL=C LANG=C LANGUAGE=C gives: ... Executed 33 tests 4 FAILED: Found

Re: Build failure

* Bram Moolenaar <b...@moolenaar.net> [2016-02-28 14:20 +0100]: > > Elimar Riesebieter wrote: [...] > > Well running this as user works as it should. So the only difference > > are the environment variables. My build wrapper has set LANG=C and > > LC_ALL=C. Setti

Re: Build failure

* Dominique Pellé <dominique.pe...@gmail.com> [2016-02-28 12:08 +0100]: > Elimar Riesebieter <riese...@lxtec.de> wrote: [...] > Can you give us a backtrace with gdb? No. Can't find a core file anywhere. > You can get it from the core file using: > > $ cd vim/src/te

Re: Build failure

* Elimar Riesebieter <riese...@lxtec.de> [2016-02-28 10:44 +0100]: > Hi all, > > I tried to build v7.4.1444 and got: > > (1 of 1): Line2^M"test_cdo.res" [New File]^[[64;16H^[[K^[[64;16H[New] 0L, 0C > written^M^M¬ > Executed 2 tests^M"messages"

Build failure

Hi all, I tried to build v7.4.1444 and got: (1 of 1): Line2^M"test_cdo.res" [New File]^[[64;16H^[[K^[[64;16H[New] 0L, 0C written^M^M¬ Executed 2 tests^M"messages"^[[64;12H^[[K^[[64;12H23L, 521C^[[64;12H^[[K^[[64;12H28L, 600C written^M^M¬ ^[[?1l^[>^[[34h^[[?25h^[[?1049lVIMRUNTIME=../../runtime;

I am really impressed

Hi Bram, hi vim devalopers, I am really impressed about how our project is moved forward. VIM can claim that it is in a good shape towards the vim-dev community. And I want want so say thanks to all who are anticipating the development and a really respectful thank to Bram, who coordinates all

Re: 7.4.1207 fails to build

* Bram Moolenaar <b...@moolenaar.net> [2016-01-30 18:11 +0100]: > > Elimar Riesebieter wrote: > > > > Huge build on linux: > > > > > > on.c:52:43: warning: macro "__DATE__" might prevent reproducible builds > > > [-Wdate-ti

7.4.1207 fails to build

Huge build on linux: on.c:52:43: warning: macro "__DATE__" might prevent reproducible builds [-Wdate-time] char *longVersion = VIM_VERSION_LONG_DATE __DATE__ " " __TIME__ ")"; ^ version.c:52:56: warning: macro "__TIME__" might prevent reproducible

Re: 7.4.1207 fails to build

* Elimar Riesebieter <riese...@lxtec.de> [2016-01-30 17:06 +0100]: > Huge build on linux: > > on.c:52:43: warning: macro "__DATE__" might prevent reproducible builds > [-Wdate-time] > char *longVersion = VIM_VERSION_

Re: 7.4.1207 fails to build

* Bram Moolenaar <b...@moolenaar.net> [2016-01-30 17:32 +0100]: > > Elimar Riesebieter wrote: > > > Huge build on linux: > > > > on.c:52:43: warning: macro "__DATE__" might prevent reproducible builds > > [-Wdate-time] > > char *lo

Re: Patch 7.4.1010

* Bram Moolenaar [2015-12-31 20:46 +0100]: > > Patch 7.4.1010 > Problem:Some developers are unhappy while running tests. > Solution: Add a test and some color. > Files: src/ex_cmds.c, src/testdir/test_assert.vim Do you want to push v7.4.1016 at midnight? Elimar

Re: Patch 7.4.1010

* Bram Moolenaar [2015-12-31 20:46 +0100]: > > Patch 7.4.1010 > Problem:Some developers are unhappy while running tests. > Solution: Add a test and some color. > Files: src/ex_cmds.c, src/testdir/test_assert.vim > > > *** ../vim-7.4.1009/src/ex_cmds.c

Re: Patch 7.4.1010

* Bram Moolenaar <b...@moolenaar.net> [2015-12-31 22:57 +0100]: > > Elimar Riesebieter wrote: > > > * Bram Moolenaar <b...@moolenaar.net> [2015-12-31 20:46 +0100]: > > > > > > > > Patch 7.4.1010 > > > Problem:Some developers a

Re: [patch] test 49 failed building 7.4.989 on linux

* Elimar Riesebieter <riese...@lxtec.de> [2015-12-29 14:31 +0100]: > * Christian Brabandt <cbli...@256bit.org> [2015-12-29 13:33 +0100]: > > > Hi Elimar! > > > > On Di, 29 Dez 2015, Elimar Riesebieter wrote: > > > > > As I don't know how the

Re: [patch] test 49 failed building 7.4.989 on linux

* Christian Brabandt <cbli...@256bit.org> [2015-12-29 13:33 +0100]: > Hi Elimar! > > On Di, 29 Dez 2015, Elimar Riesebieter wrote: > > > As I don't know how the G's in test49.in are working here is a > > patch against test49.ok. > > > > Elimar >

[patch] test 49 failed building 7.4.989 on linux

As I don't know how the G's in test49.in here is a patch against test499.ok. Elimar -- On the keyboard of life you have always to keep a finger at the escape key;-) -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying

Re: [vim] propose vim as manpager that syntax highlights and follows symlinks (#491)

* Christian Brabandt [2015-11-20 12:34 -0800]: > what is the difference with e.g. > http://www.drchip.org/astronaut/vim/index.html#MANPAGEVIEW? > Here is what I use in my shell: function vman() { command man $* | col -b | /usr/bin/view -c 'set ft=man nomod nolist'

Re: Patch 7.4.956

* Christian Brabandt [2015-12-05 13:06 +0100]: > On Fr, 04 Dez 2015, Bram Moolenaar wrote: [...] > #v+ > ~/code/vim$ git log -p -1 -r v7.4.956 runtime/filetype.vim > commit f882d9f89dbe24ab1ba4bc88529bef28242fd2ed > Author: Bram Moolenaar > Date: Thu Dec 3

Re: tags problem has followed us from hg

* toothpik [2015-09-09 20:04 -0500]: > I used to sometimes have a problem with the tags module when we were > under hg, and I had a specific set of things I did to get around it > > it seems the problem has followed us to git -- here's my pull: > > Wed 19:30

Re: tags problem has followed us from hg

* Elimar Riesebieter <riese...@lxtec.de> [2015-09-10 16:54 +0200]: [...] > If you have local changes you > can create your own branch like "git branch -b $(yourbranch)" and > archive your branch then. Should be "git checkout -b $(yourbranch)" Elimar -- &

Re: Patch 7.4.749

* Bram Moolenaar b...@moolenaar.net [2015-06-20 15:30 +0200]: Patch 7.4.749 (after 7.4.741) Problem:For some options two consecutive commas are OK. (Nikolay Pavlov) Solution: Add the P_ONECOMMA flag. Files: src/option.c This patch is missing in git? commit

Re: Preparations for moving to github

* James McCoy james...@jamessan.com [2015-03-26 11:26 -0400]: [...] $ git clone https://github.com/vim/vim ... $ cd vim $ du -hs .git . 685M.git 47M . $ git gc --aggressive ... $ du -hs .git . 34M .git 47M . For reference, are similar numbers for a fresh Mercurial

Re: Preparations for moving to github

* Bram Moolenaar b...@moolenaar.net [2015-03-24 22:36 +0100]: Since Google Code is going to be shut down we need a new place for the Vim repository. Many users have given their opinion and github appears to be the preferred site. This is not without disadvantages, since it means moving

Re: Preparations for moving to github

* Bram Moolenaar b...@moolenaar.net [2015-03-24 22:36 +0100]: Since Google Code is going to be shut down we need a new place for the Vim repository. Many users have given their opinion and github appears to be the preferred site. This is not without disadvantages, since it means moving

7.4.428: normal.c:4521:36: error: 'p_sbr' undeclared

Trying to build a tiny version gives me: normal.c: In function 'nv_screengo': normal.c:4521:36: error: 'p_sbr' undeclared (first use in this function) if (virtcol (colnr_T)width1 *p_sbr != NUL) ^ normal.c:4521:36: note: each undeclared identifier is

Re: 7.4.428: normal.c:4521:36: error: 'p_sbr' undeclared

* Bram Moolenaar b...@moolenaar.net [2014-08-30 13:32 +0200]: Elimar Riesebieter wrote: Trying to build a tiny version gives me: normal.c: In function 'nv_screengo': normal.c:4521:36: error: 'p_sbr' undeclared (first use in this function) if (virtcol (colnr_T)width1 *p_sbr

Re: Patch 7.4.326

* Bram Moolenaar b...@moolenaar.net [2014-06-14 12:55 +0200]: Patch 7.4.326 Builds fine ;-) Thanks Elimar -- Experience is something you don't get until just after you need it! -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text

7.4.324: TINY build fails

gcc (Debian 4.9.0-6) 4.9.0 Copyright (C) 2014 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. gcc -c -I. -Iproto -DHAVE_CONFIG_H -g -O2 -fstack-protector

test87 failed

Hi all, I've tried to build a Debian package with both python/dyn and python3/dyn. The Debian build uses shadowdirs. A single build is like that: #!/bin/sh /usr/bin/make -C src shadow SHADOWDIR=vim-nox \ cd src/vim-nox \ LDFLAGS=-Wl,-z,relro CPPFLAGS= CFLAGS=-g -O2 -fstack-protector \

Re: Vim 7.4b not getting any syntax or other default files

* Sazid Al Rashid sazido...@gmail.com [2013-07-31 01:25 -0700]: Recently, I compiled Vim 7.4b with Python, Ruby, Lua, Perl and huge feature list. But, in Ubuntu 13.04, when I open Vim 7.4b, it complains that the syntax.vim file could not be loaded. Moreover, it did not load the other things,

Re: [PATCH] (3/3) _vim_runtimepath_ special directory and some small stuff

* Jun T. takimot...@kba.biglobe.ne.jp [2013-06-13 13:42 +0900]: [...] In addition, if I configure --with-python3interp=dynamic, test87 core dumps. This core dump can be fixed by the following patch: diff -r 8a49630c8a5f src/if_python3.c --- a/src/if_python3.cWed Jun 12 22:41:37

Re: test86 failures using python 2.7.5

* James McCoy james...@jamessan.com [2013-06-11 23:12 -0400]: I just tried updating Debian's packages to 7.3.1169 and ran into the attached failures for test86. There is a core dump left running test87. To reproduce run $ ../vim.nox -u unix.vim -U NONE --noplugin -s dotest.in test87.in This

Re: Patch 7.3.1080

* Bram Moolenaar b...@moolenaar.net [2013-05-31 20:49 +0200]: [...] Note that this solves it by commenting out a function that apparently fails. I hope you can figure out why it fails, so we can re-enable the tests. [...] * Jun T. takimot...@kba.biglobe.ne.jp [2013-06-06 10:39 +0900]: Hi

Re: Patch 7.3.1080

* Bram Moolenaar b...@moolenaar.net [2013-05-31 20:49 +0200]: I wrote: Patch 7.3.1080 Problem:Test 86 fails. Solution: Comment out the parts that don't work. Make it pass on 32 bit systems. Files: src/testdir/test86.in, src/testdir/test86.ok Note that

Re: Patch 7.3.1042

* Bram Moolenaar b...@moolenaar.net [2013-05-29 22:02 +0200]: Patch 7.3.1042 Problem:Python: can't assign to vim.Buffer.name. Solution: Python patch 3. (ZyX) Files:runtime/doc/if_pyth.txt, src/ex_cmds.c, src/if_py_both.h, src/if_python3.c, src/if_python.c,

Re: Patch 7.3.697

* Ike Devolder ike.devol...@gmail.com [2012-10-21 12:47 +0200]: On Sunday, October 21, 2012 01:40:45 AM Bram Moolenaar wrote: [...] the attached patch fixes the problem Confirmed Elimar -- The path to source is always uphill! -unknown- -- You received

Re: Patch 7.2.181

* Bram Moolenaar [090517 16:23 +0200] Patch 7.2.181 Problem:Some more compiler warnings when using gcc -Wextra. Solution: Add UNUSED and type casts. Files:src/if_mzsch.c, src/gui.c, src/gui_gtk.c, src/gui_gtk_x11.c, src/gui_gtk_f.c, src/gui_beval.c,

Re: Regression introduced in patch 7.2.50: fwrite() failures incorrectly checked

* Dominique Pelle [081129 09:10 +0100] Tests 58 and 59 fail when doing 'make test' with latest Vim-7.2.55 (huge version, tested on Linux). I tried older versions: - Vim-7.2.49 All tests pass - Vim-7.2.50 Tests 58 59 fail. Same here: Test results: test58 FAILED test59

Re: Regression introduced in patch 7.2.50: fwrite() failures incorrectly checked

* Dominique Pelle [081129 16:40 +0100] [...] The attached patch makes the tests 58 and 59 succeed, by doing Confirmed Elimar -- On the keyboard of life you have always to keep a finger at the escape key;-) --~--~-~--~~~---~--~~ You received this message

Re: patch 7.1.036

On Fri, 27 Jul 2007 the mental interface of Bram Moolenaar told: [...] I test with about 30 different configurations, and they all work fine. I suspect you build with some specific features enabled or disabled. You'll have to tell use exactly how you build to be able to understand what is

Re: patch 7.1.036

On Tue, 24 Jul 2007 the mental interface of Bram Moolenaar told: Patch 7.1.036 Problem:Completing :echohl argument should include None. (Ori Avtalion) :match should have none too. Solution: Add flags to use expand_highlight(). Also fix that when disabling

<    1   2