ZyX | 19 Apr 18:16 2014
Picon

[BUG] Inconsistent number in Invalid operation error messages

Consider the following two operations:

    echo {} > {}
    echo [] > []

. In first case Vim will report

    E736: Invalid operation for Dictionary

(singular form). In the second case Vim will report

    E692: Invalid operation for Lists

(*plural* form).

-- 
--

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

Andrew | 19 Apr 15:47 2014
Picon

"_dd doesn't reset v:register

Given a text file with the following two lines:

    first line
    second line

If you now go to the second line and yank it, then go to the first line and type in

    "_ddp

What I'd expect to happen is:

    second line
    second line

What actually happens is:

    second line

The `p` doesn't do anything at all, unless you press it a second time.

After some experimentation, I figured out that the `v:register` variable is not reset after the `"_dd`
operation. As a result, the following `p` uses the `_` register. This is reproducible with other
registers as well. If you do anything after the `"_dd` (like move down one line with `j`), the register is
reset just fine and `p` uses the default one.

The original issue that brought this to my attention is here if you'd like more context: https://github.com/AndrewRadev/whitespaste.vim/issues/2

-- 
--

-- 
You received this message from the "vim_dev" maillist.
(Continue reading)

Christian Brabandt | 17 Apr 17:26 2014

[patch] append($, 'foobar') does not return an error

Bram,
I accidentally called append($, 'foobar') and was surprised the string 
was actually entered at the top. I did rather expect E116 invalid 
arguments for function append.

So here is a patch:

diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt
--- a/runtime/doc/eval.txt
+++ b/runtime/doc/eval.txt
 <at>  <at>  -3982,7 +3982,8  <at>  <at>  libcallnr({libname}, {funcname}, {argume
  <
  							*line()*
  line({expr})	The result is a Number, which is the line number of the 
file
-		position given with {expr}.  The accepted positions are:
+		position given with {expr}. Returns -1 in case of an invalid
+		position. The accepted positions are:
  		    .	    the cursor position
  		    $	    the last line in the current buffer
  		    'x	    position of mark x (if the mark is not set, 0 is
diff --git a/src/eval.c b/src/eval.c
--- a/src/eval.c
+++ b/src/eval.c
 <at>  <at>  -8813,7 +8813,10  <at>  <at>  f_append(argvars, rettv)
  	    curwin->w_cursor.lnum += added;
      }
      else
+    {
+	EMSG(N_("E116: Invalid arguments for function append"));
(Continue reading)

Ken Takata | 17 Apr 12:53 2014
Picon

[patch] possible bug in gui_mch_init() in gui_gtk_x11.c

Hi,

Clang warns this:

--- a/src/gui_gtk_x11.c
+++ b/src/gui_gtk_x11.c
 <at>  <at>  -3163,7 +3163,7  <at>  <at> 
 # if defined(FEAT_FLOAT) && defined(LC_NUMERIC)
 	/* Make sure strtod() uses a decimal point, not a comma. Gnome init
 	 * may change it. */
-	if (setlocale(LC_NUMERIC, NULL) != (char *) "C")
+	if (strcmp(setlocale(LC_NUMERIC, NULL), "C") != 0)
 	   setlocale(LC_NUMERIC, "C");
 # endif
     }

Regards,
Ken Takata

-- 
--

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

Matthew Martin | 17 Apr 10:12 2014
Picon

digraph.txt: line uses spaces instead of tabs

In digraph.txt line 1080 (MIDLINE HORIZONTAL ELLIPSIS) is aligned with spaces instead of tabs. Every
other line is tab aligned.

-- 
--

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

Peleg Michaeli | 16 Apr 15:41 2014
Picon

Separating highlighting colours for `showcmd`, command line and normal text

Currently, the only way to control the colour of the `showcmd` characters which
are displayed at the bottom line on the right, is via the `Normal` highlight
group (as far as I know).

Since making it more obvious that vim is still waiting for keys to complete the
command could be beneficial, I was hoping that one day I could highlight it
differently.

Saying this, it would be even nicer to separate the highlight groups used for
the command line (perhaps even a different one for the cases `/` and `?` than
for the case of `:` - but that doesn't sound that important), for the `Normal`
text mode, and for the `showcmd` output.

If `ModeMsg` and `ErrorMsg` are allowed, why `CommandLine` and `Command` will
not be allowed as well?

-- 
--

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

Stephen Braithwaite | 17 Apr 02:46 2014
Picon

I would like to add AES to available encryptions. Would such an addition be welcome?

I am a programmer, and would like to add AES to available encryptions, which currently is mostly only
blowfish.  
Would such an addition be welcome?  
Would such a patch contributed by me be acceptable?
Or are there good reasons why VIM should have only blowfish, and the original encryption available in VIM
which is known to be broken, and whose name I have forgotten?

-- 
--

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

David Fishburn | 16 Apr 04:15 2014
Picon

Enabling Python on Windows

Been building Vim for years, trying to get the Python builds to work and am failing.

I can't see what is wrong, the parameters I pass to make a pretty clear.
I know I have built with Python in the past and not much has changed.

If anyone can see anything for me to try it would be appreciated.


Vim 7.4.1-258

:echo has('python') has('python2') has('python3')
0 0 0

C:\OpenSrc\vim\src>which python27.dll
c:\Python27\python27.dll


C:\OpenSrc>dir c:\Python27
 Volume in drive C is OSDisk
 Volume Serial Number is E8F1-79E4

 Directory of c:\Python27

13/04/2014  07:57 PM    <DIR>          .
13/04/2014  07:57 PM    <DIR>          ..
13/04/2014  07:56 PM    <DIR>          DLLs
18/09/2012  02:51 PM    <DIR>          Doc
18/09/2012  02:51 PM    <DIR>          include
03/02/2014  02:27 PM    <DIR>          Lib
18/09/2012  02:51 PM    <DIR>          libs
02/10/2013  10:05 AM    <DIR>          Scripts
18/09/2012  02:51 PM    <DIR>          tcl
18/09/2012  02:51 PM    <DIR>          Tools
10/04/2012  11:31 PM            40,092 LICENSE.txt
10/04/2012  11:18 PM           310,875 NEWS.txt
10/04/2012  11:24 PM            27,136 python.exe
06/04/2013  07:55 PM         3,003,392 python27.dll
10/04/2012  11:24 PM            27,648 pythonw.exe
18/03/2012  11:58 PM            54,973 README.txt


nmake -f Make_mvc.mak debug=no gui=yes cscope=yes OLE=yes FEATURES=HUGE PYTHON=C:\Python27 DYNAMIC_PYTHON=yes PYTHON_VER=27 PERL=C:\Perl DYNAMIC_PERL=yes PERL_VER=510 XPM=xpm\x86 clean




:ver
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr 13 2014 20:37:47)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-258
Compiled by me
Huge version with GUI.  Features included (+) or not (-):
+acl             +cmdline_compl   +diff            +find_in_path    +langmap         +mouse           -postscript      +signs           -tcl             +visualextra     +xpm_w32
+arabic          +cmdline_hist    +digraphs        +float           +libcall         +mouseshape      +printer         +smartindent     -tgetent         +viminfo
+autocmd         +cmdline_info    -dnd             +folding         +linebreak       +multi_byte      +profile         -sniff           -termresponse    +vreplace
+balloon_eval    +comments        -ebcdic          -footer          +lispindent      +multi_lang      +python/dyn      +startuptime     +textobjects     +wildignore
+browse          +conceal         +emacs_tags      +gettext/dyn     +listcmds        -mzscheme        -python3         +statusline      +title           +wildmenu
++builtin_terms  +cryptv          +eval            -hangul_input    +localmap        +netbeans_intg   +quickfix        -sun_workshop    +toolbar         +windows
+byte_offset     +cscope          +ex_extra        +iconv/dyn       -lua             +ole             +reltime         +syntax          +user_commands   +writebackup
+cindent         +cursorbind      +extra_search    +insert_expand   +menu            +path_extra      +rightleft       +tag_binary      +vertsplit       -xfontset
+clientserver    +cursorshape     +farsi           +jumplist        +mksession       +perl/dyn        -ruby            +tag_old_static  +virtualedit     -xim
+clipboard       +dialog_con_gui  +file_in_path    +keymap          +modify_fname    +persistent_undo +scrollbind      -tag_any_white   +visual          -xterm_save
   system vimrc file: "$VIM\vimrc"
     user vimrc file: "$HOME\_vimrc"
 2nd user vimrc file: "$HOME\vimfiles\vimrc"
 3rd user vimrc file: "$VIM\_vimrc"
      user exrc file: "$HOME\_exrc"
  2nd user exrc file: "$VIM\_exrc"
  system gvimrc file: "$VIM\gvimrc"
    user gvimrc file: "$HOME\_gvimrc"
2nd user gvimrc file: "$HOME\vimfiles\gvimrc"
3rd user gvimrc file: "$VIM\_gvimrc"
    system menu file: "$VIMRUNTIME\menu.vim"
Compilation: cl -c /W3 /nologo  -I. -Iproto -DHAVE_PATHDEF -DWIN32   -DFEAT_CSCOPE -DFEAT_NETBEANS_INTG   -DFEAT_XPM_W32   -DWINVER=0x0400 -D_WIN32_WINNT=0x0400  /Fo.\ObjGOLYi386/ /Ox /GL
-DNDEBUG  /Zl /MT -DFEAT_OLE -DFEAT_GUI_W32 -DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_PYTHON -DDYNAMIC_PYTHON  -DDYNAMIC_PYTHON_DLL=\"python27.dll\" -DFEAT_PERL -DDYNAMIC_PERL -DDYNAMIC_PER
L_DLL=\"perl510.dll\" -DFEAT_HUGE /Fd.\ObjGOLYi386/ /Zi
Linking: link /RELEASE /nologo /subsystem:windows /LTCG:STATUS oldnames.lib kernel32.lib advapi32.lib shell32.lib gdi32.lib  comdlg32.lib ole32.lib uuid.lib /machine:i386 /nodefaultlib gdi
32.lib version.lib   winspool.lib comctl32.lib advapi32.lib shell32.lib  /machine:i386 /nodefaultlib libcmt.lib oleaut32.lib  user32.lib      /nodefaultlib:python27.lib     WSock32.lib xpm
\x86\lib\libXpm.lib /PDB:gvim.pdb -debug


Thanks,
David

--
--
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.
Dominic Humphries | 14 Apr 12:29 2014
Picon

Bug: Misinterpretation of key sequence

Entering the commands to leave insert mode & insert a new line above the current one, beginning with certain
letters, results in punctuation on the current line instead.

To reproduce:
Start vim, *quickly* type the keys: i<Esc>Om

Expected result:
New line created above the current one with the letter 'm' in it

Actual result:
Hyphen inserted on current line

Also affects:
Letters j,k,n,o
j gives *, k gives +, m gives -, n gives ., o gives /

Vim version: 7.4 (as installed by Ubuntu 13.10)
Happens on my machine, my co-worker's machine, several VMs and to some (not all) of the people I asked about
it on IRC. Definitely requires that the typing is done quickly. Causes me problems very frequently
because I write a lot of Perl and when I go to declare a variable, I get "-y $foo" on the current line instead of
"my $foo" on the previous line.

-- 
--

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

Tony Mechelynck | 14 Apr 08:29 2014
Picon

Error under :help has-patch

Under :help has-patch, the new ยง4 says:

> 4.  Beyond a certain version or at a certain version and including a specific
>     patch.  The "patch-7.4.123" feature means that the Vim version is 7.5 or
>     later, or it is version 7.4 and patch 123 was included.
>     The example above can be simplified to: >
> 	:if has("patch-6.2.148")
> <    Note that it's possible for patch 147 to be omitted even though 148 is
>     included.

Well, the problem with using :if has("patch-6.2.148") is that this form 
of the test was only introduced at patchlevel 7.4.236 (and corrected at 
7.4.237). Vim 6.2 to 7.4.235 wouldn't know what has("patch-6.2.148") 
meant, and therefore, I suppose, return 0 (i.e. false) unconditionally, 
even with the patch in place. For patchlevels earlier than 7.4.237 it is 
better to use the former test, :if version > 602 || (version == 602 && 
has("patch148")), which still works on later versions anyway.

Best regards,
Tony.
-- 
Say my love is easy had,
	Say I'm bitten raw with pride,
Say I am too often sad --
	Still behold me at your side.

Say I'm neither brave nor young,
	Say I woo and coddle care,
Say the devil touched my tongue --
	Still you have my heart to wear.

But say my verses do not scan,
	And I get me another man!
		-- Dorothy Parker, "Fighting Words"

-- 
--

-- 
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 | 12 Apr 13:13 2014
Picon
Picon

Patch 7.4.258


Patch 7.4.258
Problem:    Configure fails if $CC contains options.
Solution:   Remove quotes around $CC. (Paul Barker)
Files:	    src/configure.in, src/auto/configure

*** ../vim-7.4.257/src/configure.in	2014-04-10 20:00:03.708106386 +0200
--- src/configure.in	2014-04-12 13:00:51.332428899 +0200
***************
*** 46,55 ****
  fi
  if test "$GCC" = yes; then
    dnl method that should work for nearly all versions
!   gccversion=`"$CC" -dumpversion`
    if test "x$gccversion" = "x"; then
      dnl old method; fall-back for when -dumpversion doesn't work
!     gccversion=`"$CC" --version | sed -e '2,$d' -e 's/darwin.//' -e 's/^[[^0-9]]*\([[0-9]]\.[[0-9.]]*\).*$/\1/g'`
    fi
    dnl version 4.0.1 was reported to cause trouble on Macintosh by Marcin Dalecki
    if test "$gccversion" = "3.0.1" -o "$gccversion" = "3.0.2" -o "$gccversion" = "4.0.1"; then
--- 46,55 ----
  fi
  if test "$GCC" = yes; then
    dnl method that should work for nearly all versions
!   gccversion=`$CC -dumpversion`
    if test "x$gccversion" = "x"; then
      dnl old method; fall-back for when -dumpversion doesn't work
!     gccversion=`$CC --version | sed -e '2,$d' -e 's/darwin.//' -e 's/^[[^0-9]]*\([[0-9]]\.[[0-9.]]*\).*$/\1/g'`
    fi
    dnl version 4.0.1 was reported to cause trouble on Macintosh by Marcin Dalecki
    if test "$gccversion" = "3.0.1" -o "$gccversion" = "3.0.2" -o "$gccversion" = "4.0.1"; then
***************
*** 68,74 ****
  dnl the version number of the clang in use.
  dnl Note that this does not work to get the version of clang 3.1 or 3.2.
  AC_MSG_CHECKING(for recent clang version)
! CLANG_VERSION_STRING=`"$CC" --version 2>/dev/null | sed  -n -e 's/^.*clang.*\([[0-9]][[0-9]]*\.[[0-9]][[0-9]]*\.[[0-9]][[0-9]]*\).*$/\1/p'`
  if test x"$CLANG_VERSION_STRING" != x"" ; then
    CLANG_MAJOR=`echo "$CLANG_VERSION_STRING" | sed -n -e 's/\([[0-9]][[0-9]]*\)\.[[0-9]][[0-9]]*\.[[0-9]][[0-9]]*/\1/p'`
    CLANG_MINOR=`echo "$CLANG_VERSION_STRING" | sed -n -e 's/[[0-9]][[0-9]]*\.\([[0-9]][[0-9]]*\)\.[[0-9]][[0-9]]*/\1/p'`
--- 68,74 ----
  dnl the version number of the clang in use.
  dnl Note that this does not work to get the version of clang 3.1 or 3.2.
  AC_MSG_CHECKING(for recent clang version)
! CLANG_VERSION_STRING=`$CC --version 2>/dev/null | sed  -n -e 's/^.*clang.*\([[0-9]][[0-9]]*\.[[0-9]][[0-9]]*\.[[0-9]][[0-9]]*\).*$/\1/p'`
  if test x"$CLANG_VERSION_STRING" != x"" ; then
    CLANG_MAJOR=`echo "$CLANG_VERSION_STRING" | sed -n -e 's/\([[0-9]][[0-9]]*\)\.[[0-9]][[0-9]]*\.[[0-9]][[0-9]]*/\1/p'`
    CLANG_MINOR=`echo "$CLANG_VERSION_STRING" | sed -n -e 's/[[0-9]][[0-9]]*\.\([[0-9]][[0-9]]*\)\.[[0-9]][[0-9]]*/\1/p'`
*** ../vim-7.4.257/src/auto/configure	2014-04-10 20:00:03.716106386 +0200
--- src/auto/configure	2014-04-12 13:00:58.436428915 +0200
***************
*** 4074,4082 ****
    test "$GCC" = yes && CFLAGS="-O2 -fno-strength-reduce -Wall"
  fi
  if test "$GCC" = yes; then
!     gccversion=`"$CC" -dumpversion`
    if test "x$gccversion" = "x"; then
!         gccversion=`"$CC" --version | sed -e '2,$d' -e 's/darwin.//' -e 's/^[^0-9]*\([0-9]\.[0-9.]*\).*$/\1/g'`
    fi
      if test "$gccversion" = "3.0.1" -o "$gccversion" = "3.0.2" -o "$gccversion" = "4.0.1"; then
      echo 'GCC [34].0.[12] has a bug in the optimizer, disabling "-O#"'
--- 4074,4082 ----
    test "$GCC" = yes && CFLAGS="-O2 -fno-strength-reduce -Wall"
  fi
  if test "$GCC" = yes; then
!     gccversion=`$CC -dumpversion`
    if test "x$gccversion" = "x"; then
!         gccversion=`$CC --version | sed -e '2,$d' -e 's/darwin.//' -e 's/^[^0-9]*\([0-9]\.[0-9.]*\).*$/\1/g'`
    fi
      if test "$gccversion" = "3.0.1" -o "$gccversion" = "3.0.2" -o "$gccversion" = "4.0.1"; then
      echo 'GCC [34].0.[12] has a bug in the optimizer, disabling "-O#"'
***************
*** 4091,4097 ****

  { $as_echo "$as_me:${as_lineno-$LINENO}: checking for recent clang version" >&5
  $as_echo_n "checking for recent clang version... " >&6; }
! CLANG_VERSION_STRING=`"$CC" --version 2>/dev/null | sed  -n -e 's/^.*clang.*\([0-9][0-9]*\.[0-9][0-9]*\.[0-9][0-9]*\).*$/\1/p'`
  if test x"$CLANG_VERSION_STRING" != x"" ; then
    CLANG_MAJOR=`echo "$CLANG_VERSION_STRING" | sed -n -e 's/\([0-9][0-9]*\)\.[0-9][0-9]*\.[0-9][0-9]*/\1/p'`
    CLANG_MINOR=`echo "$CLANG_VERSION_STRING" | sed -n -e 's/[0-9][0-9]*\.\([0-9][0-9]*\)\.[0-9][0-9]*/\1/p'`
--- 4091,4097 ----

  { $as_echo "$as_me:${as_lineno-$LINENO}: checking for recent clang version" >&5
  $as_echo_n "checking for recent clang version... " >&6; }
! CLANG_VERSION_STRING=`$CC --version 2>/dev/null | sed  -n -e 's/^.*clang.*\([0-9][0-9]*\.[0-9][0-9]*\.[0-9][0-9]*\).*$/\1/p'`
  if test x"$CLANG_VERSION_STRING" != x"" ; then
    CLANG_MAJOR=`echo "$CLANG_VERSION_STRING" | sed -n -e 's/\([0-9][0-9]*\)\.[0-9][0-9]*\.[0-9][0-9]*/\1/p'`
    CLANG_MINOR=`echo "$CLANG_VERSION_STRING" | sed -n -e 's/[0-9][0-9]*\.\([0-9][0-9]*\)\.[0-9][0-9]*/\1/p'`
*** ../vim-7.4.257/src/version.c	2014-04-12 12:26:25.856424387 +0200
--- src/version.c	2014-04-12 13:05:09.372429463 +0200
***************
*** 736,737 ****
--- 736,739 ----
  {   /* Add new patch number below this line */
+ /**/
+     258,
  /**/

-- 
Never go to the toilet in a paperless office.

 /// Bram Moolenaar -- Bram <at> Moolenaar.net -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org        ///
 \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

-- 
--

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


Gmane