Re: Vim 7.4a ready for beta testing (test96 FAILED)

2013-07-07 Fir de Conversatie raf
Bram Moolenaar wrote: > Announcing: Vim (Vi IMproved) version 7.4a BETA > > This is the first BETA release of Vim 7.4. > > Please check that the distribution is OK. I haven't done one for a long > time. Report anything that isn't right. That includes a crash but also > a typo in the document

Re:

2013-07-07 Fir de Conversatie tux-
Tony Mechelynck schrob am Sonntag, 7. Juli 2013 um 16:47 Zeit: > Did you install, or at leat run, your new Vim, to see its version? Yup, it's 7.3.. > I think it's "C:\Program Files\Vim\vim74a" or something, NOT > ...\vim73 as it used to be. Yep, it is, I manually renamed the folder. But you f

Re:

2013-07-07 Fir de Conversatie Tony Mechelynck
On 07/07/13 16:39, tux- wrote: Tony Mechelynck schrob am Sonntag, 7. Juli 2013 um 16:22 Zeit: Are you sure your "current" changeset ("hg log -r ." without the quotes) is on the default branch and is a descendant of v7-4a-001? "hg tags" says 7.4 is current. :-/ The "hg up" command did not chan

Re: Patch 7.4a.001

2013-07-07 Fir de Conversatie Tony Mechelynck
On 07/07/13 16:16, Bram Moolenaar wrote: Patch 7.4a.002 Problem:Valgrind errors in test 89. (Simon Ruderich) Solution: Allocate one more byte. (Dominique Pelle) Files: src/misc2.c Notwithstanding the email's Subject, this is indeed patch 7.4a.002. Best regards, Tony. -- The doctri

Re:

2013-07-07 Fir de Conversatie tux-
Tony Mechelynck schrob am Sonntag, 7. Juli 2013 um 16:22 Zeit: > Are you sure your "current" changeset ("hg log -r ." without the quotes) > is on the default branch and is a descendant of v7-4a-001? "hg tags" says 7.4 is current. :-/ The "hg up" command did not change anything, version.h also say

Re:

2013-07-07 Fir de Conversatie Tony Mechelynck
On 07/07/13 15:26, tux- wrote: Tony Mechelynck schrob am Sonntag, 7. Juli 2013 um 06:53 Zeit: You should already have it. Oh, right, thanks! But why does it still "make" 7.3? :-/ (I use MS Windows, VS 2010.) Oh, does it? Mine (on Linux) doesn't. Try doing a full make (i.e., telling Make t

Patch 7.4a.001

2013-07-07 Fir de Conversatie Bram Moolenaar
Patch 7.4a.002 Problem:Valgrind errors in test 89. (Simon Ruderich) Solution: Allocate one more byte. (Dominique Pelle) Files: src/misc2.c *** ../vim-7.4a.001/src/misc2.c 2013-07-04 21:14:48.0 +0200 --- src/misc2.c 2013-07-07 16:03:35.0 +0200 *** *** 4712,4

Re:

2013-07-07 Fir de Conversatie tux-
Tony Mechelynck schrob am Sonntag, 7. Juli 2013 um 06:53 Zeit: > You should already have it. Oh, right, thanks! But why does it still "make" 7.3? :-/ (I use MS Windows, VS 2010.) -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you

Re: Valgrind errors in test89

2013-07-07 Fir de Conversatie Bram Moolenaar
Dominique Pelle wrote: > Bram Moolenaar wrote: > > > > > Simon Ruderich wrote: > > > >> Hello, > >> > >> Running the testsuite for the latest Vim (7.4a.1) shows these > >> errors when running test89: > >> > >> ==10670== Invalid write of size 1 > >> ==10670==at 0x4C29552: strcpy (in

Re: Can't open remote file on VimEnter

2013-07-07 Fir de Conversatie glts
On Sun, Jul 7, 2013 at 1:05 PM, Tony Mechelynck wrote: > On 07/07/13 13:02, Tony Mechelynck wrote: >> >> On 07/07/13 12:07, glts wrote: >>> >>> On Sun, Jul 7, 2013 at 11:44 AM, glts <676c7...@gmail.com> wrote: Trying to :read a remote file on VimEnter results in Error dete

Re: Can't open remote file on VimEnter

2013-07-07 Fir de Conversatie glts
On Sun, Jul 7, 2013 at 1:07 PM, Bram Moolenaar wrote: > > David Burgin wrote: > >> Trying to :read a remote file on VimEnter results in >> >> Error detected while processing VimEnter Auto commands for "*": >> E484: Can't open file http://www.openssh.org/txt/rfc1349.txt >> >> I used the fol

Re: Valgrind errors in test89

2013-07-07 Fir de Conversatie Dominique Pellé
Bram Moolenaar wrote: > > Simon Ruderich wrote: > >> Hello, >> >> Running the testsuite for the latest Vim (7.4a.1) shows these >> errors when running test89: >> >> ==10670== Invalid write of size 1 >> ==10670==at 0x4C29552: strcpy (in >> /usr/lib/valgrind/vgpreload_memcheck-amd64-li

Re: [PATCH] syntax/help.vim: Use concealends for helpExample to conceal > markers.

2013-07-07 Fir de Conversatie Bram Moolenaar
Simon Ruderich wrote: > Resending this patch. > > It conceals the "<" and ">" markers in the help syntax. Useful > for terminal emulators with pseudo transparency like urxvt. It > supports Vim without the conceal feature. Hmm, I suppose that should work. Let's include it and check it doesn't c

Re: [patch] fix typos in 7.4a

2013-07-07 Fir de Conversatie Bram Moolenaar
Ken Takata wrote: > Additional fixes here. Thanks! -- It is illegal for anyone to give lighted cigars to dogs, cats, and other domesticated animal kept as pets. [real standing law in Illinois, United States of America] /// Bram Moolenaar -- b...@moolenaar.net -- http://www.M

Re: [PATCH] doc/options.txt: Fix typo in 'list' description.

2013-07-07 Fir de Conversatie Bram Moolenaar
Simon Ruderich wrote: > diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt > index 72eaeef..21cc352 100644 > --- a/runtime/doc/options.txt > +++ b/runtime/doc/options.txt > @@ -4646,7 +4646,7 @@ A jump table for the options with a short description= > can be found at |Q_op|. >

Re: Patch 7.3.1294

2013-07-07 Fir de Conversatie Bram Moolenaar
ZyX wrote: > Just mentioned: help file (:h diffoff) still says that options are > restore to their default values. Right, I forgot to update that. -- The Law, in its majestic equality, forbids the rich, as well as the poor, to sleep under the bridges, to beg in the streets, and to steal bread.

Re: Valgrind errors in test89

2013-07-07 Fir de Conversatie Bram Moolenaar
Simon Ruderich wrote: > Hello, > > Running the testsuite for the latest Vim (7.4a.1) shows these > errors when running test89: > > ==10670== Invalid write of size 1 > ==10670==at 0x4C29552: strcpy (in > /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) > ==10670==by 0x21

Re: Can't open remote file on VimEnter

2013-07-07 Fir de Conversatie Bram Moolenaar
David Burgin wrote: > Trying to :read a remote file on VimEnter results in > > Error detected while processing VimEnter Auto commands for "*": > E484: Can't open file http://www.openssh.org/txt/rfc1349.txt > > I used the following minimal vimrc with Vim 7.4a. > > filetype plugin in

Re: Can't open remote file on VimEnter

2013-07-07 Fir de Conversatie Tony Mechelynck
On 07/07/13 13:02, Tony Mechelynck wrote: On 07/07/13 12:07, glts wrote: On Sun, Jul 7, 2013 at 11:44 AM, glts <676c7...@gmail.com> wrote: Trying to :read a remote file on VimEnter results in Error detected while processing VimEnter Auto commands for "*": E484: Can't open file http:/

Re: Can't open remote file on VimEnter

2013-07-07 Fir de Conversatie Tony Mechelynck
On 07/07/13 12:07, glts wrote: On Sun, Jul 7, 2013 at 11:44 AM, glts <676c7...@gmail.com> wrote: Trying to :read a remote file on VimEnter results in Error detected while processing VimEnter Auto commands for "*": E484: Can't open file http://www.openssh.org/txt/rfc1349.txt I used th

Re: Can't open remote file on VimEnter

2013-07-07 Fir de Conversatie glts
On Sun, Jul 7, 2013 at 11:44 AM, glts <676c7...@gmail.com> wrote: > Trying to :read a remote file on VimEnter results in > > Error detected while processing VimEnter Auto commands for "*": > E484: Can't open file http://www.openssh.org/txt/rfc1349.txt > > I used the following minimal vimrc

Can't open remote file on VimEnter

2013-07-07 Fir de Conversatie glts
Trying to :read a remote file on VimEnter results in Error detected while processing VimEnter Auto commands for "*": E484: Can't open file http://www.openssh.org/txt/rfc1349.txt I used the following minimal vimrc with Vim 7.4a. filetype plugin indent on autocmd VimEnter * read ht

[REQ] Provide a separate highlight occasion for the showbreak option

2013-07-07 Fir de Conversatie Axel Bender
It would be helpful to be able to highlight the indicator for continuation lines (showbreak) differently from that of the EOT markers (~, @). While the first indicator usually profits from a good visibility, the latter preferably uses some dim colors. At the moment there exists only one hightlig