Re: paredit.vim
Could you add paredit : http://www.vim.org/scripts/script.php?script_id=3998 to the vim plugin runtime files ? I'd rather vote for adding an official package manager and leave it to the users to decide whether they want to add this plugin. -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Vim stops
Marcin said: I am not sure why it get's three Z though. I'd expected to see only two of them. The last z eats the first Z, if there are an odd number of z's, as z is a prefix to two key commands. Regards, John Little -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: :rubydo X fail on Mac OS X 10.7.5
I confirm that : $ sudo make install STRIP=/usr/bin/true Work's fine. Why I've never see this command on other topics with all the people complaining that vim doesn't work well with ruby + os X ? I will try this night on an older macbook running OS X 10.6.7 Thanks for the reply. Le lundi 8 juillet 2013 13:25:03 UTC+2, Timothee Gauthier a écrit : Hi, I compile Vim on OS X with the latest version, but when I do in vim every rubydo command: :rubydo puts x It crash with Vim: Caught deadly signal TRAP Vim: Finished. vim --version VIM - Vi IMproved 7.4a BETA (2013 Jul 6, compiled Jul 8 2013 10:54:48) MacOS X (unix) version Included patches: 1-2 Compiled by tim@plop Big version without GUI. Features included (+) or not (-): ...[removed long description] +diff+menu+ruby+writebackup ...[removed long description] system vimrc file: $VIM/vimrc user vimrc file: $HOME/.vimrc 2nd user vimrc file: ~/.vim/vimrc user exrc file: $HOME/.exrc fall-back for $VIM: /usr/local/share/vim Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DMACOS_X_UNIX -no-cpp-precomp -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 Linking: gcc -L. -L/Users/tim/.rbenv/versions/2.0.0-p195/lib -L/usr/local/lib -o vim-lm -lncurses -liconv -framework Cocoa -framework Python -lruby-static -lobjc -L/Users/tim/.rbenv/versions/2.0.0-p195/lib I run on Mac OS X 10.7.5 (on Intel) ruby --version (compiled with rbenv) ruby 2.0.0p195 (2013-05-14 revision 40734) [x86_64-darwin11.4.2] Since I m new in the compiling world, I print what I've made: hg pull hg update make clean ./configure --with-features=HUGE --enable-rubyinterp make sudo make install And I also tried /configure --with-features=HUGE \ --enable-multibyte=yes \ --enable-cscope=yes \ --enable-rubyinterp=yes \ --with-ruby-command=/Users/tim/.rbenv/versions/2.0.0-p195/bin/ruby \ And it end with the same problem. Do you need more datas to help me ? Thank you. -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: :rubydo X fail on Mac OS X 10.7.5
You said it's because of ruby 2.0, But I tried to compile with ruby 1.8.7 (on the system) and 1.9.3, and it ends with the same problem. Thanks for the solution. Le lundi 8 juillet 2013 18:20:36 UTC+2, Kent Sibilev a écrit : On Monday, July 8, 2013 7:25:03 AM UTC-4, Timothee Gauthier wrote: Hi, I compile Vim on OS X with the latest version, but when I do in vim every rubydo command: :rubydo puts x It crash with Vim: Caught deadly signal TRAP Vim: Finished. When you install vim, ask it not to strip symbol table: $ sudo make install STRIP=/usr/bin/true For some reason ruby 2.0 has problems with that. BR, Kent -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[NFA] Slow Regexp with many branches
Hi list,
I noticed that using Vim 7.4a the Vimwiki plugin works measurably slower with
re=0 than with re=1. I figured out the reason is this regexp in the syntax
definition:
[[:alnum:]]\@!\%(\%(\%(http\|https\|file\|ftp\|gopher\|telnet\|nntp\|ldap\|rsync\|imap\|pop\|irc\|ircs\|cvs\|svn\|svn+ssh\|git\|ssh\|fish\|sftp\):\%(\/\/\)\)\|\%(mailto\|news\|xmpp\|sip\|sips\|doi\|urn\|tel\):\)\S\{-1,}\%(([^
\t()]*)\)\=\S*
You may know what it is supposed to match.
Removing some of the branches makes it faster and so does removing
[[:alnum:]]\@!
I don't know if there is a standard method for measuring speed of the syntax
highlight, but here is what I have done:
- open a relatively large file
- :set syn=off
- :syntax match Number
/[[:alnum:]]\@!\%(\%(\%(http\|https\|file\|ftp\|gopher\|telnet\|nntp\|ldap\|rsync\|imap\|pop\|irc\|ircs\|cvs\|svn\|svn+ssh\|git\|ssh\|fish\|sftp\):\%(\/\/\)\)\|\%(mailto\|news\|xmpp\|sip\|sips\|doi\|urn\|tel\):\)\S\{-1,}\%(([^
\t()]*)\)\=\S*/
- scroll with c-e and c-y
- extremely slow with re=0 but normal slow (*wink*) with re=1
So, can this behavior be considered as a bug?
--
--
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Breaking undo in Insert mode
Ben Fritz wrote: On Mon, Jul 8, 2013 at 1:59 PM, Bram Moolenaar b...@moolenaar.net wrote: Benjamin Fritz wrote: On Thu, Jul 4, 2013 at 4:44 AM, Bram Moolenaar b...@moolenaar.net wrote: Does the delimitMate return the text to be inserted or does it use setline()? In the last case it can't be fixed really. It actually uses setline(). Why? What does it do that can't be done by returning a string? Type: iabc( get (where | is the cursor): abc(|) now continue typing 123) + 456; get: abc(123) + 456;| Note how the parenthesis got inserted automatically, but manually entering ) did not insert a second ) but rather moved the cursor over the existing one. That can be done by returning cursor key sequences. No need for setline(): imap ( C-R=LeftParen()CR fun! LeftParen() return ()\Left endfun imap ) C-R=RightParen()CR fun! RightParen() return \Right endfun -- Violators can be fined, arrested or jailed for making ugly faces at a dog. [real standing law in Oklahoma, United States of America] /// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Patch 7.4a.003
Patch 7.4a.003
Problem:Copyright year is oudated.
Solution: Only use the first year.
Files: src/vim.rc, src/vim16.rc
*** ../vim-7.4a.002/src/vim.rc 2013-06-16 16:37:33.0 +0200
--- src/vim.rc 2013-07-08 20:38:16.0 +0200
***
*** 91,97
VALUE FileDescription,Vi Improved - A Text Editor\0
VALUE FileVersion,VIM_VERSION_MAJOR_STR ,
VIM_VERSION_MINOR_STR , VIM_VERSION_BUILD_STR ,
VIM_VERSION_PATCHLEVEL_STR \0
VALUE InternalName, VIM\0
! VALUE LegalCopyright, Copyright \251 1996-2008\0
VALUE LegalTrademarks,Vim\0
VALUE OriginalFilename, VIM.EXE\0
VALUE ProductName,Vim\0
--- 91,97
VALUE FileDescription,Vi Improved - A Text Editor\0
VALUE FileVersion,VIM_VERSION_MAJOR_STR ,
VIM_VERSION_MINOR_STR , VIM_VERSION_BUILD_STR ,
VIM_VERSION_PATCHLEVEL_STR \0
VALUE InternalName, VIM\0
! VALUE LegalCopyright, Copyright \251 1996\0
VALUE LegalTrademarks,Vim\0
VALUE OriginalFilename, VIM.EXE\0
VALUE ProductName,Vim\0
*** ../vim-7.4a.002/src/vim16.rc2010-05-15 13:04:08.0 +0200
--- src/vim16.rc2013-07-08 20:39:05.0 +0200
***
*** 67,73
VALUE FileDescription,Vi Improved - A Text Editor\0
VALUE FileVersion,VIM_VERSION_MAJOR_STR ,
VIM_VERSION_MINOR_STR , VIM_VERSION_BUILD_STR ,
VIM_VERSION_PATCHLEVEL_STR \0
VALUE InternalName, VIM\0
! VALUE LegalCopyright, Copyright \251 1996-2005\0
VALUE LegalTrademarks,Vim\0
VALUE OriginalFilename, VIM.EXE\0
VALUE ProductName,Vim\0
--- 67,73
VALUE FileDescription,Vi Improved - A Text Editor\0
VALUE FileVersion,VIM_VERSION_MAJOR_STR ,
VIM_VERSION_MINOR_STR , VIM_VERSION_BUILD_STR ,
VIM_VERSION_PATCHLEVEL_STR \0
VALUE InternalName, VIM\0
! VALUE LegalCopyright, Copyright \251 1996\0
VALUE LegalTrademarks,Vim\0
VALUE OriginalFilename, VIM.EXE\0
VALUE ProductName,Vim\0
*** ../vim-7.4a.002/src/version.c 2013-07-07 16:15:29.0 +0200
--- src/version.c 2013-07-09 12:53:34.0 +0200
***
*** 730,731
--- 730,733
{ /* Add new patch number below this line */
+ /**/
+ 3,
/**/
--
Dogs must have a permit signed by the mayor in order to congregate in groups
of three or more on private property.
[real standing law in Oklahoma, United States of America]
/// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [patch][7.4a] Copyright information in vim.rc is old
On 08/07/13 20:59, Bram Moolenaar wrote: Ken Takata wrote: Copyright year in vim.rc (and vim16.rc) seems old. I think it's better to move to version.h. Please check the attached patch. Actually, I have been told that only the first year matters. So we can just keep 1996. Note that under current international legislation, no © statement is required anymore; all original literary works (including program sources) are automatically protected until 50 years (in the European Union, 70 years) starting at 00:00 hours on the 1st of January following the author's death (and, for collective works, the death of the last known author). I'm not sure if it's 00:00 UTC or 00:00 local time. Bram is a Dutchman, and there are other authors for at least some parts of the work, but local laws apply wherever you make a copy. Best regards, Tony. -- The intelligence of any discussion diminishes with the square of the number of participants. -- Adam Walinsky -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [patch] add support for Microsoft Visual Studio 2012 Update 3
Raymond Ko wrote: The following mini-patch adds support for Microsoft Visual Studio 2012 Update 3, which has bumped their version number in the compiler. I have tested this and can confirm that a vim executable is successfully produced. Thanks, I'll include it. -- Lawmakers made it obligatory for everybody to take at least one bath each week -- on Saturday night. [real standing law in Vermont, United States of America] /// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Patch 7.4a.004
Patch 7.4a.004
Problem:MSVC 2012 Update 3 is not recognized.
Solution: Add the version number. (Raymond Ko)
Files: src/Make_mvc.mak
*** ../vim-7.4a.003/src/Make_mvc.mak2013-06-03 20:09:58.0 +0200
--- src/Make_mvc.mak2013-07-09 13:13:12.0 +0200
***
*** 421,426
--- 421,429
!if $(_NMAKE_VER) == 11.00.60315.1
MSVCVER = 11.0
!endif
+ !if $(_NMAKE_VER) == 11.00.60610.1
+ MSVCVER = 11.0
+ !endif
!endif
# Abort building VIM if version of VC is unrecognised.
*** ../vim-7.4a.003/src/version.c 2013-07-09 12:54:17.0 +0200
--- src/version.c 2013-07-09 13:13:52.0 +0200
***
*** 730,731
--- 730,733
{ /* Add new patch number below this line */
+ /**/
+ 4,
/**/
--
Beeth Girls are like internet domain names,
the ones I like are already taken.
honx Well, you can stil get one from a strange country :-P
/// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [patch][7.4a] Copyright information in vim.rc is old
Tony Mechelynck wrote: On 08/07/13 20:59, Bram Moolenaar wrote: Ken Takata wrote: Copyright year in vim.rc (and vim16.rc) seems old. I think it's better to move to version.h. Please check the attached patch. Actually, I have been told that only the first year matters. So we can just keep 1996. Note that under current international legislation, no Š statement is required anymore; all original literary works (including program sources) are automatically protected until 50 years (in the European Union, 70 years) starting at 00:00 hours on the 1st of January following the author's death (and, for collective works, the death of the last known author). I'm not sure if it's 00:00 UTC or 00:00 local time. Bram is a Dutchman, and there are other authors for at least some parts of the work, but local laws apply wherever you make a copy. The copyright statement is not needed to obtain copyright, but to explain to the reader who has claimed copyright. This does matter in case things turn bad. In practice there has never been any copyright dispute over files in the Vim distribution. -- I know that there are people who don't love their fellow man, and I hate those people! - Tom Lehrer /// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [patch] 'scrollbind' causes unexpected scroll of one of the windows
Lech Lorens wrote: On 30-Jun-2013 Lech Lorens lech.lor...@gmail.com wrote: On 30-Jun-2013 Bram Moolenaar b...@moolenaar.net wrote: The fix seems OK. But the test already passes without it. Yes, this is what I tried to explain above but somehow didn't make it clear ;-) Also, the test changes the window height, which is nasty. Yeah, since the test doesn't work anyway, I didn't bother to make it prettier here. Perhaps you can make it work by forcing a redraw? I did try. I'll try using a debugger to find out why it doesn't work. Perhaps then I can find out how to make it work. I did use a debugger to find out that using normal-mode commands triggers a different kind of redraw than using command-mode commands (i.e. :source! causes different behaviour than :source). I worked the problem around by introducing a helper file which is sourced by the test. Perhaps this approach is acceptable. The attached patch includes a fix and a test which fails before applying the fix and succeeds afterwards. Thanks. I verified the test fails without the patch. -- If you only have a hammer, you tend to see every problem as a nail. If you only have MS-Windows, you tend to solve every problem by rebooting. /// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Patch 7.4a.005
Patch 7.4a.005
Problem:Scroll binding causes unexpected scroll.
Solution: Store the topline after updating scroll binding. Add a test.
(Lech Lorens)
Files: src/testdir/test98.in, src/testdir/test98a.in,
src/testdir/test98.ok, src/option.c, src/testdir/Make_amiga.mak,
src/testdir/Make_dos.mak, src/testdir/Make_ming.mak,
src/testdir/Make_os2.mak, src/testdir/Make_vms.mms,
src/testdir/Makefile
*** ../vim-7.4a.004/src/testdir/test98.in 2013-07-09 13:44:23.0
+0200
--- src/testdir/test98.in 2013-07-09 13:35:26.0 +0200
***
*** 0
--- 1,21
+ Test for 'scrollbind' causing an unexpected scroll of one of the windows.
+ STARTTEST
+ :so small.vim
+ :source test98a.in
+ :let topLineLeft = line('w0')
+ :wincmd p
+ :let topLineRight = line('w0')
+ :setl noscrollbind
+ :wincmd p
+ :setl noscrollbind
+ :q!
+ :%del _
+ :call setline(1, 'Difference between the top lines (left - right): ' .
string(topLineLeft - topLineRight))
+ :w! test.out
+ :brewind
+ ENDTEST
+
+ STARTTEST
+ :qa!
+ ENDTEST
+
*** ../vim-7.4a.004/src/testdir/test98a.in 2013-07-09 13:44:23.0
+0200
--- src/testdir/test98a.in 2013-07-09 13:33:06.0 +0200
***
*** 0
--- 1,27
+ We don't want the status line to cause problems:
+ set laststatus=0
+ redraw!
+ let g:totalLines = lines * 20
+ let middle = g:totalLines / 2
+ wincmd n
+ wincmd o
+ for i in range(1, g:totalLines)
+ call setline(i, 'LINE ' . i)
+ endfor
+
+ exe string(middle)
+ normal zt
+ normal M
+
+ aboveleft vert new
+ for i in range(1, g:totalLines)
+ call setline(i, 'line ' . i)
+ endfor
+ exe string(middle)
+ normal zt
+ normal M
+ setl scb
+
+ wincmd p
+
+ call feedkeys(:setl scb\n\C-w\C-w, 't')
*** ../vim-7.4a.004/src/testdir/test98.ok 2013-07-09 13:44:23.0
+0200
--- src/testdir/test98.ok 2013-07-09 13:36:08.0 +0200
***
*** 0
--- 1
+ Difference between the top lines (left - right): 0
*** ../vim-7.4a.004/src/option.c2013-07-03 15:35:37.0 +0200
--- src/option.c2013-07-09 13:38:16.0 +0200
***
*** 7801,7807
--- 7801,7810
else if ((int *)varp == curwin-w_p_scb)
{
if (curwin-w_p_scb)
+ {
do_check_scrollbind(FALSE);
+ curwin-w_scbind_pos = curwin-w_topline;
+ }
}
#endif
*** ../vim-7.4a.004/src/testdir/Make_amiga.mak 2013-07-03 16:21:39.0
+0200
--- src/testdir/Make_amiga.mak 2013-07-09 13:40:02.0 +0200
***
*** 33,39
test76.out test77.out test78.out test79.out test80.out \
test81.out test82.out test83.out test84.out test88.out \
test89.out test90.out test91.out test92.out test93.out \
! test94.out test95.out test96.out test97.out
.SUFFIXES: .in .out
--- 33,39
test76.out test77.out test78.out test79.out test80.out \
test81.out test82.out test83.out test84.out test88.out \
test89.out test90.out test91.out test92.out test93.out \
! test94.out test95.out test96.out test97.out test98.out
.SUFFIXES: .in .out
***
*** 147,149
--- 147,150
test95.out: test95.in
test96.out: test96.in
test97.out: test97.in
+ test98.out: test98.in
*** ../vim-7.4a.004/src/testdir/Make_dos.mak2013-07-03 20:17:26.0
+0200
--- src/testdir/Make_dos.mak2013-07-09 13:40:30.0 +0200
***
*** 32,38
test79.out test80.out test81.out test82.out test83.out \
test84.out test85.out test86.out test87.out test88.out \
test89.out test90.out test91.out test92.out test93.out \
! test94.out test95.out test96.out
SCRIPTS32 = test50.out test70.out
--- 32,38
test79.out test80.out test81.out test82.out test83.out \
test84.out test85.out test86.out test87.out test88.out \
test89.out test90.out test91.out test92.out test93.out \
! test94.out test95.out test96.out test98.out
SCRIPTS32 = test50.out test70.out
*** ../vim-7.4a.004/src/testdir/Make_ming.mak 2013-07-03 20:17:22.0
+0200
--- src/testdir/Make_ming.mak 2013-07-09 13:40:38.0 +0200
***
*** 52,58
test79.out test80.out test81.out test82.out test83.out \
test84.out test85.out test86.out test87.out test88.out \
test89.out test90.out test91.out test92.out test93.out \
! test94.out test95.out test96.out
SCRIPTS32 = test50.out test70.out
--- 52,58
test79.out test80.out test81.out test82.out test83.out \
test84.out test85.out test86.out test87.out test88.out \
test89.out test90.out test91.out test92.out
Patch 7.4a.006
Patch 7.4a.006
Problem:Failure in po file check goes unnoticed.
Solution: Fail make test if the po file check fails.
Files: src/Makefile
*** ../vim-7.4a.005/src/Makefile2013-07-06 14:33:40.0 +0200
--- src/Makefile2013-07-09 14:54:43.0 +0200
***
*** 1850,1856
#
test check:
$(MAKE) -f Makefile $(VIMTARGET)
! -if test -n $(MAKEMO) -a -f $(PODIR)/Makefile; then \
cd $(PODIR); $(MAKE) -f Makefile check VIM=../$(VIMTARGET); \
fi
-if test $(VIMTARGET) != vim -a ! -r vim; then \
--- 1850,1856
#
test check:
$(MAKE) -f Makefile $(VIMTARGET)
! if test -n $(MAKEMO) -a -f $(PODIR)/Makefile; then \
cd $(PODIR); $(MAKE) -f Makefile check VIM=../$(VIMTARGET); \
fi
-if test $(VIMTARGET) != vim -a ! -r vim; then \
*** ../vim-7.4a.005/src/version.c 2013-07-09 13:44:40.0 +0200
--- src/version.c 2013-07-09 14:56:07.0 +0200
***
*** 730,731
--- 730,733
{ /* Add new patch number below this line */
+ /**/
+ 6,
/**/
--
ARTHUR: If you do not open these doors, we will take this castle by force ...
[A bucket of slops land on ARTHUR. He tries to retain his dignity.]
Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Russian translation for Vim 7.4
Sergey Alyoshin wrote: Updated Russian translation for Vim 7.4 Thanks! -- Living on Earth includes an annual free trip around the Sun. /// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [NFA] Slow Regexp with many branches
Grüner_Gimpel wrote:
I noticed that using Vim 7.4a the Vimwiki plugin works measurably
slower with re=0 than with re=1. I figured out the reason is this
regexp in the syntax definition:
[[:alnum:]]\@!\%(\%(\%(http\|https\|file\|ftp\|gopher\|telnet\|nntp\|ldap\|rsync\|imap\|pop\|irc\|ircs\|cvs\|svn\|svn+ssh\|git\|ssh\|fish\|sftp\):\%(\/\/\)\)\|\%(mailto\|news\|xmpp\|sip\|sips\|doi\|urn\|tel\):\)\S\{-1,}\%(([^
\t()]*)\)\=\S*
You may know what it is supposed to match.
Removing some of the branches makes it faster and so does removing
[[:alnum:]]\@!
I don't know if there is a standard method for measuring speed of the
syntax highlight, but here is what I have done:
- open a relatively large file
- :set syn=off
- :syntax match Number
/[[:alnum:]]\@!\%(\%(\%(http\|https\|file\|ftp\|gopher\|telnet\|nntp\|ldap\|rsync\|imap\|pop\|irc\|ircs\|cvs\|svn\|svn+ssh\|git\|ssh\|fish\|sftp\):\%(\/\/\)\)\|\%(mailto\|news\|xmpp\|sip\|sips\|doi\|urn\|tel\):\)\S\{-1,}\%(([^
\t()]*)\)\=\S*/
- scroll with c-e and c-y
- extremely slow with re=0 but normal slow (*wink*) with re=1
So, can this behavior be considered as a bug?
The main problem is the [[:alnum:]]\@! item. Have you tried adding a
limit? Should be [[:alnum:]]\@1!
Or perhaps using \ instead will work.
For measuring times: use :syntime.
--
No children may attend school with their breath smelling of wild onions.
[real standing law in West Virginia, United States of America]
/// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [NFA] Slow Regexp with many branches
On Jul 9, 2013 4:58 PM, Bram Moolenaar b...@moolenaar.net wrote:
Grüner_Gimpel wrote:
I noticed that using Vim 7.4a the Vimwiki plugin works measurably
slower with re=0 than with re=1. I figured out the reason is this
regexp in the syntax definition:
[[:alnum:]]\@!\%(\%(\%(http\|https\|file\|ftp\|gopher\|telnet\|nntp\|ldap\|rsync\|imap\|pop\|irc\|ircs\|cvs\|svn\|svn+ssh\|git\|ssh\|fish\|sftp\):\%(\/\/\)\)\|\%(mailto\|news\|xmpp\|sip\|sips\|doi\|urn\|tel\):\)\S\{-1,}\%(([^
\t()]*)\)\=\S*
You may know what it is supposed to match.
Removing some of the branches makes it faster and so does removing
[[:alnum:]]\@!
I don't know if there is a standard method for measuring speed of the
syntax highlight, but here is what I have done:
- open a relatively large file
- :set syn=off
- :syntax match Number
/[[:alnum:]]\@!\%(\%(\%(http\|https\|file\|ftp\|gopher\|telnet\|nntp\|ldap\|rsync\|imap\|pop\|irc\|ircs\|cvs\|svn\|svn+ssh\|git\|ssh\|fish\|sftp\):\%(\/\/\)\)\|\%(mailto\|news\|xmpp\|sip\|sips\|doi\|urn\|tel\):\)\S\{-1,}\%(([^
\t()]*)\)\=\S*/
- scroll with c-e and c-y
- extremely slow with re=0 but normal slow (*wink*) with re=1
So, can this behavior be considered as a bug?
The main problem is the [[:alnum:]]\@! item. Have you tried adding a
limit? Should be [[:alnum:]]\@1!
Or perhaps using \ instead will work.
For measuring times: use :syntime.
Could not it deduce a limit by itself in such simple cases?
--
No children may attend school with their breath smelling of wild onions.
[real standing law in West Virginia, United States of
America]
/// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
--
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
k moves to incorrect column after g$
Hi list, 1. vim -nNX -u NONE 2. :se ve=all 3. 3otestesc 4. g$ Then I expect k to move me up in the same column but it goes at $ in the previous line. Note: in step 4 if I move to g$ using l then k moves the cursor correctly Cheers PS: VIM - Vi IMproved 7.4a BETA (2013 Jul 6, compiled Jul 8 2013 13:51:44) Included patches: 1-2 Dimitar --- GPG Key: 2048R/160C6FA8 2012-10-11 Dimitar Dimitrov (kurkale6ka) mitk...@yahoo.fr -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Vim 7.4a ready for beta testing (test96 FAILED)
Raf wrote: 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 documentation or a missing file. mid-2010 macbookpro macosx-10.6.8 gcc-4.2.1 obtained vim-7.4a.002 via hg (same result via ftp). configure \ --disable-darwin \ --with-x \ --enable-gui=motif \ --enable-multibyte \ --with-mac-arch=current \ --with-features=huge \ --disable-acl Test results: test96 FAILED TEST FAILURE diff -u test96.ok test96.failed --- test96.ok 2013-07-08 10:12:36.0 +1000 +++ test96.failed 2013-07-08 10:15:31.0 +1000 @@ -4,6 +4,8 @@ - quickfix claims that the file name displayed is: test://bar.txt Test B: - number of window open: 2 +Test B: + - number of window open: 2 Test C: - 'buftype' of the location list window: quickfix - buffer displayed in the 2nd window: test://quux.txt i.e. the Test B section of the file is repeated. That's strange. Please check that your version of src/testdir/test96.in is the same as https://code.google.com/p/vim/source/browse/src/testdir/test96.in p.s. ftp.vim.org:pub/vim/unstable/patxhes/7.4a/MD5 doesn't contain an md5 sum for 7.4a.002 (but MD5SUMS does). Fixed that. The script had wrong dependencies (always was that way but someone only became a problem this time). -- Why is abbreviation such a long word? /// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [NFA] Slow Regexp with many branches
Nikolay Pavlov wrote:
On Jul 9, 2013 4:58 PM, Bram Moolenaar b...@moolenaar.net wrote:
Grüner_Gimpel wrote:
I noticed that using Vim 7.4a the Vimwiki plugin works measurably
slower with re=0 than with re=1. I figured out the reason is this
regexp in the syntax definition:
[[:alnum:]]\@!\%(\%(\%(http\|https\|file\|ftp\|gopher\|telnet\|nntp\|ldap\|rsync\|imap\|pop\|irc\|ircs\|cvs\|svn\|svn+ssh\|git\|ssh\|fish\|sftp\):\%(\/\/\)\)\|\%(mailto\|news\|xmpp\|sip\|sips\|doi\|urn\|tel\):\)\S\{-1,}\%(([^
\t()]*)\)\=\S*
You may know what it is supposed to match.
Removing some of the branches makes it faster and so does removing
[[:alnum:]]\@!
I don't know if there is a standard method for measuring speed of the
syntax highlight, but here is what I have done:
- open a relatively large file
- :set syn=off
- :syntax match Number
/[[:alnum:]]\@!\%(\%(\%(http\|https\|file\|ftp\|gopher\|telnet\|nntp\|ldap\|rsync\|imap\|pop\|irc\|ircs\|cvs\|svn\|svn+ssh\|git\|ssh\|fish\|sftp\):\%(\/\/\)\)\|\%(mailto\|news\|xmpp\|sip\|sips\|doi\|urn\|tel\):\)\S\{-1,}\%(([^
\t()]*)\)\=\S*/
- scroll with c-e and c-y
- extremely slow with re=0 but normal slow (*wink*) with re=1
So, can this behavior be considered as a bug?
The main problem is the [[:alnum:]]\@! item. Have you tried adding a
limit? Should be [[:alnum:]]\@1!
Or perhaps using \ instead will work.
For measuring times: use :syntime.
Could not it deduce a limit by itself in such simple cases?
It does, but I'm not sure what patterns it works for:
nfa_max_width()
--
Another bucket of what can only be described as human ordure hits ARTHUR.
ARTHUR: ... Right! (to the KNIGHTS) That settles it!
Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Patch 7.4a.006
After this patch, build was failed like this Mismatching error/warning code in line 3006 make[2]: *** [nl.ck] Error 1 make[2]: Leaving directory `/home/travis/build/vim-jp/vim-ci/vim/src/po' make[1]: *** [test] Error 2 Check this for details: https://travis-ci.org/vim-jp/vim-ci/jobs/8886799 -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
7.4a - Confirm dialog box larger than screen size
I believe I saw this fixed earlier, or something related.
I have tested this with:
:ver
VIM - Vi IMproved 7.4a BETA (2013 Jul 6, compiled Jul 9 2013 09:34:36)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-6
Compiled by me
Big version with GUI. Features included (+) or not (-):
Run on Windows 7 x64.
gvim.exe -u NONE -U NONE
Open Vim.
Resize Vim so that the top and bottom of the Vim window is nearly maximized.
Or
Simply maximize Vim by double clicking on the title bar.
Run the following:
:echo confirm('Test'.repeat(\nNext line, 80))
This will produce a dialog box with a scrollbar within it.
The scrolling of the items is correct.
But, there are 2 issues.
1. Assuming your taskbar is at the default windows position (bottom of
screen) then window is much longer than than the window size. Many of the
Next lines are off the screen and the OK button is no where to be seen.
2. If you taskbar is at the top of the screen (as mine always is) then the
problem may stem from the same issue of being too large, but there is an
additional problem. The top of the window is underneath the taskbar, so
you cannot click on it to move it. Many of the Next lines are off the
screen and the OK button is no where to be seen.
Please make sure Vim has either been maximized or nearly the length of the
screen first. If you do not, you will not see the same behaviour. The
confirm modal window is larger than Vim, but it will not exceed screen size
if Vim isn't using most of screen real-estate.
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: k moves to incorrect column after g$
On Tue, July 9, 2013 15:15, Dimitar DIMITROV wrote: Hi list, 1. vim -nNX -u NONE 2. :se ve=all 3. 3otestesc 4. g$ Then I expect k to move me up in the same column but it goes at $ in the previous line. Note: in step 4 if I move to g$ using l then k moves the cursor correctly Cheers PS: VIM - Vi IMproved 7.4a BETA (2013 Jul 6, compiled Jul 8 2013 13:51:44) Included patches: 1-2 I see. This patch fixes it. regards, Christian -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. g.diff Description: Binary data
Re: k moves to incorrect column after g$
Dimitar Dimitrov wrote: Hi list, 1. vim -nNX -u NONE 2. :se ve=all 3. 3otestesc 4. g$ Then I expect k to move me up in the same column but it goes at $ in the previous line. Note: in step 4 if I move to g$ using l then k moves the cursor correctly Cheers PS: VIM - Vi IMproved 7.4a BETA (2013 Jul 6, compiled Jul 8 2013 13:51:44) Included patches: 1-2 It only works that way after: :set nowrap It is documented, but it's not really what one expects. -- ARTHUR: CHARGE! [The mighty ARMY charges. Thundering noise of feet. Clatter of coconuts. Shouts etc. Suddenly there is a wail of a siren and a couple of police cars roar round in front of the charging ARMY and the POLICE leap out and stop them. TWO POLICEMAN and the HISTORIAN'S WIFE. Black Marias skid up behind them.] HISTORIAN'S WIFE: They're the ones, I'm sure. Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [patch] fix typos in 7.4a
Hi, One more patch attached :-) 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. # HG changeset patch # Parent 072432e9e2137750a4b0cfde20323b7ad4542ffd diff --git a/runtime/doc/version7.txt b/runtime/doc/version7.txt --- a/runtime/doc/version7.txt +++ b/runtime/doc/version7.txt @@ -11730,7 +11730,7 @@ Files: src/fileio.c Patch 7.3.261 -Problem:G++ error message errornously recognized as error. +Problem:G++ error message erroneously recognized as error. Solution: Ignore In file included from line also when it ends in a colon. (Fernando Castillo) Files: src/option.h @@ -13682,7 +13682,7 @@ Patch 7.3.604 Problem:inputdialog() doesn't use the cancel argument in the console. (David Fishburn) -Solution: Use the third argument. (Christian Brabant) +Solution: Use the third argument. (Christian Brabandt) Files: src/eval.c Patch 7.3.605 (after 7.3.577) @@ -15523,7 +15523,7 @@ Problem:Autocommands are triggered by setwinvar() et al. Missing BufEnter on :tabclose. Duplicate WinEnter on :tabclose. Wrong order of events for :tablose and :tabnew. -Solution: Fix these autocommand events. (Zyx) +Solution: Fix these autocommand events. (ZyX) Files: runtime/doc/eval.txt, src/buffer.c, src/eval.c, src/ex_cmds2.c, src/fileio.c, src/proto/window.pro, src/testdir/test62.in, src/testdir/test62.ok, src/window.c
[Patch] Fix Python indentation with trailing TODO comments
File: runtime/indent/python.vim
When checking for a colon at the end of a statement to decide whether to indent
the next line, it strips trailing comments; however, the syntax group can be
pythonTodo rather than pythonComment, which it was not detecting.
Thus, a line like this:
if True: # TODO
would lead to the next line not being indented an extra level, which is not
correct.
The simple solution (employed here) is to change the check for `Comment$` to
`(Comment|Todo)$`. A more complex but
more-correct-in-case-of-user-extensions-to-the-syntax solution would check the
whole synstack, but I deemed that as probably unnecessary. I'm happy to write
such a thing if desired, though.
This has been an issue for quite some time, probably since the beginning of
that syntax file.
--
--
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
*** runtime/indent/python.vim 2013-07-09 23:14:48.209114454 +1000
--- new.python.vim 2013-07-09 23:22:45.719482300 +1000
***
*** 2,8
Language: Python
Maintainer: Bram Moolenaar b...@vim.org
Original Author: David Bustos bus...@caltech.edu
! Last Change: 2013 Jun 21
Only load this indent file when no other was loaded.
if exists(b:did_indent)
--- 2,8
Language: Python
Maintainer: Bram Moolenaar b...@vim.org
Original Author: David Bustos bus...@caltech.edu
! Last Change: 2013 Jul 9
Only load this indent file when no other was loaded.
if exists(b:did_indent)
***
*** 61,67
let parlnum = searchpair('(\|{\|\[', '', ')\|}\|\]', 'nbW',
\ line('.') . (plnum - s:maxoff) . ? dummy :
\ . synIDattr(synID(line('.'), col('.'), 1), 'name')
! \ . =~ '\\(Comment\\|String\\)$')
if parlnum 0
let plindent = indent(parlnum)
let plnumstart = parlnum
--- 61,67
let parlnum = searchpair('(\|{\|\[', '', ')\|}\|\]', 'nbW',
\ line('.') . (plnum - s:maxoff) . ? dummy :
\ . synIDattr(synID(line('.'), col('.'), 1), 'name')
! \ . =~ '\\(Comment\\|Todo\\|String\\)$')
if parlnum 0
let plindent = indent(parlnum)
let plnumstart = parlnum
***
*** 80,93
let p = searchpair('(\|{\|\[', '', ')\|}\|\]', 'bW',
\ line('.') . (a:lnum - s:maxoff) . ? dummy :
\ . synIDattr(synID(line('.'), col('.'), 1), 'name')
! \ . =~ '\\(Comment\\|String\\)$')
if p 0
if p == plnum
When the start is inside parenthesis, only indent one 'shiftwidth'.
let pp = searchpair('(\|{\|\[', '', ')\|}\|\]', 'bW',
\ line('.') . (a:lnum - s:maxoff) . ? dummy :
\ . synIDattr(synID(line('.'), col('.'), 1), 'name')
! \ . =~ '\\(Comment\\|String\\)$')
if pp 0
return indent(plnum) + (exists(g:pyindent_nested_paren) ? eval(g:pyindent_nested_paren) : shiftwidth())
endif
--- 80,93
let p = searchpair('(\|{\|\[', '', ')\|}\|\]', 'bW',
\ line('.') . (a:lnum - s:maxoff) . ? dummy :
\ . synIDattr(synID(line('.'), col('.'), 1), 'name')
! \ . =~ '\\(Comment\\|Todo\\|String\\)$')
if p 0
if p == plnum
When the start is inside parenthesis, only indent one 'shiftwidth'.
let pp = searchpair('(\|{\|\[', '', ')\|}\|\]', 'bW',
\ line('.') . (a:lnum - s:maxoff) . ? dummy :
\ . synIDattr(synID(line('.'), col('.'), 1), 'name')
! \ . =~ '\\(Comment\\|Todo\\|String\\)$')
if pp 0
return indent(plnum) + (exists(g:pyindent_nested_paren) ? eval(g:pyindent_nested_paren) : shiftwidth())
endif
***
*** 108,119
If the last character in the line is a comment, do a binary search for
the start of the comment. synID() is slow, a linear search would take
too long on a long line.
! if synIDattr(synID(plnum, pline_len, 1), name) =~ Comment$
let min = 1
let max = pline_len
while min max
let col = (min + max) / 2
! if synIDattr(synID(plnum, col, 1), name) =~ Comment$
let max = col
else
let min = col + 1
--- 108,119
If the last character in the line is a comment, do a binary search for
the start of the comment. synID() is slow, a linear search would take
too long on a long line.
! if synIDattr(synID(plnum, pline_len, 1), name) =~ \\(Comment\\|Todo\\)$
let min = 1
let max = pline_len
while min max
let col = (min + max) / 2
! if synIDattr(synID(plnum, col, 1), name) =~ \\(Comment\\|Todo\\)$
let max = col
else
let min = col + 1
Re: Breaking undo in Insert mode
On Tue, Jul 9, 2013 at 5:54 AM, Bram Moolenaar b...@moolenaar.net wrote: That can be done by returning cursor key sequences. No need for setline(): imap ( C-R=LeftParen()CR fun! LeftParen() return ()\Left endfun imap ) C-R=RightParen()CR fun! RightParen() return \Right endfun I don't remember how setline() solves the problem, but just returning cursor sequences doesn't work, because it breaks undo/redo/repeat. If I insert abc(123) with mappings like, then press '.' somewhere else, I will only get the 123 inserted. Pressing 'u' after inserting abc(123) + 456 will only undo the + 456. The mappings that used to work to get around this are complicated; hence the reason I'm using a plugin instead of simple mappings; but previously somehow using setline() allowed all of undo, redo, and repeat to work as if there were not any mappings. Now only repeat works. -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Vim 7.4a ready for beta testing
On Tue, Jul 9, 2013 at 1:06 AM, glts 676c7...@gmail.com wrote: On Saturday, July 6, 2013 3:59:06 PM UTC+2, 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 documentation or a missing file. What was the last word on test86? It fails for me on Ubuntu 12.04 with 7.4a and --enable-pythoninterp. But that is expected, or is it not? And there is no workaround to make it green for the release? Easy workaround is using -fPIC or -fPIE. $ CFLAGS=-fPIE ./configure --enable-pythoninterp=yes make test -- Yukihiro Nakadaira - yukihiro.nakada...@gmail.com -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[patch][7.4a] :py3 vim.eval() doesn't handle multibyte characters properly
Hi,
:py3 vim.eval() doesn't handle multibyte characters properly
when 'encoding' is not utf-8 (e.g. cp932).
How to reproduce:
:set enc=cp932
:call setline(1, \u82a0) Set Hiragana Letter A 'あ' (U+3042 in Unicode)
:py3 import vim
:py3 print(vim.eval('getline(1)')) Printing 'あ' is expected.
Traceback (most recent call last):
File string, line 1, in module
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x82 in position 0:
invalid start byte
Attached patch fixes this problem.
Please check it.
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
# HG changeset patch
# Parent 78253a62f894866cc29a5d9a1ad88687f6464ba8
diff --git a/src/if_python3.c b/src/if_python3.c
--- a/src/if_python3.c
+++ b/src/if_python3.c
@@ -86,7 +86,8 @@
#ifndef PyString_Check
# define PyString_Check(obj) PyUnicode_Check(obj)
#endif
-#define PyString_FromString(repr) PyUnicode_FromString(repr)
+#define PyString_FromString(repr) \
+PyUnicode_Decode(repr, STRLEN(repr), ENC_OPT, NULL)
#define PyString_FromFormat PyUnicode_FromFormat
#ifndef PyInt_Check
# define PyInt_Check(obj) PyLong_Check(obj)
[patch] fix some function prototypes
Hi,
I saw the following thread in vim_use, and I found some mistakes in
function prototypes.
https://groups.google.com/d/topic/vim_use/_layXHD5hUk/discussion
Warning W8065 .\version.c 3504: Call to function 'list_features' with no
prototype in function list_version
Warning W8065 if_py_both.h 2033: Call to function 'py_list_alloc' with no
prototype in function ListConstructor
Warning W8065 if_python.c 1385: Call to function 'init_types' with no prototype
in function PythonMod_Init
Warning W8065 .\gui_w48.c 3131: Call to function 'update_im_font' with no
prototype in function gui_mch_wide_font_changed
Attached patch fixes them.
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
# HG changeset patch
# Parent a28186b29f28e8d9ce350d781037c61961745cd3
diff --git a/src/gui_w48.c b/src/gui_w48.c
--- a/src/gui_w48.c
+++ b/src/gui_w48.c
@@ -3123,7 +3123,7 @@
* 'guifont'
*/
static void
-update_im_font()
+update_im_font(void)
{
LOGFONT lf_wide;
diff --git a/src/if_py_both.h b/src/if_py_both.h
--- a/src/if_py_both.h
+++ b/src/if_py_both.h
@@ -2100,7 +2100,7 @@
}
static list_T *
-py_list_alloc()
+py_list_alloc(void)
{
list_T *ret;
@@ -5857,7 +5857,7 @@
return -1;
static int
-init_types()
+init_types(void)
{
PYTYPE_READY(IterType);
PYTYPE_READY(BufferType);
diff --git a/src/version.c b/src/version.c
--- a/src/version.c
+++ b/src/version.c
@@ -35,8 +35,6 @@
char longVersion[sizeof(VIM_VERSION_LONG_DATE) + sizeof(__DATE__)
+ sizeof(__TIME__) + 3];
-static void list_features __ARGS((void));
-
void
make_version()
{
@@ -57,6 +55,7 @@
char *longVersion = VIM_VERSION_LONG;
#endif
+static void list_features __ARGS((void));
static void version_msg __ARGS((char *s));
static char *(features[]) =
Re: [patch] fix typos in 7.4a
Ken Takata wrote: One more patch attached :-) Thanks. -- ERIC IDLE PLAYED: THE DEAD COLLECTOR, MR BINT (A VILLAGE NE'ER-DO -WELL VERY KEEN ON BURNING WITCHES), SIR ROBIN, THE GUARD WHO DOESN'T HICOUGH BUT TRIES TO GET THINGS STRAIGHT, CONCORDE (SIR LAUNCELOT'S TRUSTY STEED), ROGER THE SHRUBBER (A SHRUBBER), BROTHER MAYNARD Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: 7.4a - Confirm dialog box larger than screen size
David Fishburn wrote:
I believe I saw this fixed earlier, or something related.
I have tested this with:
:ver
VIM - Vi IMproved 7.4a BETA (2013 Jul 6, compiled Jul 9 2013 09:34:36)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-6
Compiled by me
Big version with GUI. Features included (+) or not (-):
Run on Windows 7 x64.
gvim.exe -u NONE -U NONE
Open Vim.
Resize Vim so that the top and bottom of the Vim window is nearly maximized.
Or
Simply maximize Vim by double clicking on the title bar.
Run the following:
:echo confirm('Test'.repeat(\nNext line, 80))
This will produce a dialog box with a scrollbar within it.
The scrolling of the items is correct.
But, there are 2 issues.
1. Assuming your taskbar is at the default windows position (bottom of
screen) then window is much longer than than the window size. Many of the
Next lines are off the screen and the OK button is no where to be seen.
2. If you taskbar is at the top of the screen (as mine always is) then the
problem may stem from the same issue of being too large, but there is an
additional problem. The top of the window is underneath the taskbar, so
you cannot click on it to move it. Many of the Next lines are off the
screen and the OK button is no where to be seen.
Please make sure Vim has either been maximized or nearly the length of the
screen first. If you do not, you will not see the same behaviour. The
confirm modal window is larger than Vim, but it will not exceed screen size
if Vim isn't using most of screen real-estate.
Perhaps the height computatins do not add the height of the buttons?
--
[The rest of the ARMY stand around looking at a loss.]
INSPECTOR END OF FILM: (picks up megaphone) All right! Clear off! Go on!
Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Patch 7.4a.006
Thank you for describing. Now I understand what had happended. 2013/7/10 Bram Moolenaar b...@moolenaar.net: Taro Muraoka wrote: After this patch, build was failed like this Mismatching error/warning code in line 3006 make[2]: *** [nl.ck] Error 1 make[2]: Leaving directory `/home/travis/build/vim-jp/vim-ci/vim/src/po' make[1]: *** [test] Error 2 Check this for details: https://travis-ci.org/vim-jp/vim-ci/jobs/8886799 Which is correct, the nl.po file contains errors. I pushed the corrected version to Mercurial. The error went unnoticed for a long time, since make just continued after reporting the error. -- TERRY GILLIAM PLAYED: PATSY (ARTHUR'S TRUSTY STEED), THE GREEN KNIGHT SOOTHSAYER, BRIDGEKEEPER, SIR GAWAIN (THE FIRST TO BE KILLED BY THE RABBIT) Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- b...@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/// -- MURAOKA Taro koron.kaor...@gmail.com -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Breaking undo in Insert mode
On Tuesday, July 9, 2013 10:13:22 AM UTC-5, Bram Moolenaar wrote: Ben Fritz wrote: I don't remember how setline() solves the problem, but just returning cursor sequences doesn't work, because it breaks undo/redo/repeat. Yeah, that's true. I suppose we could avoid saving for undo under certain conditions, but it's quite hard to decide what those conditions are. Perhaps when inserting a register and the cursor remains within the inserted text? Is that easier than an explicit normally the next movement would break the undo sequence but I don't want it to keystroke or command? Something like the inverse of i_CTRL-G_u. Then you could simply do something like: inoremap ( ()C-GULeft inoremap expr ) (NextChar()==')' ? \C-GU\Right : )) Really I don't care HOW it's accomplished as long as it is possible to move the cursor in insert mode one or two characters without breaking undo. If allowing limited cursor movement when inserting a register is easy enough, I can probably work with that. -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Patch 7.4a.006
How about sending e-mail contains compile error to vim-dev from travis-ci? On 7/10/13, Bram Moolenaar b...@moolenaar.net wrote: Taro Muraoka wrote: After this patch, build was failed like this Mismatching error/warning code in line 3006 make[2]: *** [nl.ck] Error 1 make[2]: Leaving directory `/home/travis/build/vim-jp/vim-ci/vim/src/po' make[1]: *** [test] Error 2 Check this for details: https://travis-ci.org/vim-jp/vim-ci/jobs/8886799 Which is correct, the nl.po file contains errors. I pushed the corrected version to Mercurial. The error went unnoticed for a long time, since make just continued after reporting the error. -- TERRY GILLIAM PLAYED: PATSY (ARTHUR'S TRUSTY STEED), THE GREEN KNIGHT SOOTHSAYER, BRIDGEKEEPER, SIR GAWAIN (THE FIRST TO BE KILLED BY THE RABBIT) Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- - Yasuhiro Matsumoto -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Patch 7.4a.007
Patch 7.4a.007
Problem:After g$ with 'virtualedit' set, k moves to a different
column. (Dimitar Dimitrov)
Solution: Set w_curswant. (Christian Brabandt)
Files: src/normal.c
*** ../vim-7.4a.006/src/normal.c2013-05-20 21:11:55.0 +0200
--- src/normal.c2013-07-09 17:00:51.0 +0200
***
*** 8220,8225
--- 8220,8230
i += ((curwin-w_virtcol - width1) / width2 + 1)
* width2;
coladvance((colnr_T)i);
+
+ /* Make sure we stick in this column. */
+ validate_virtcol();
+ curwin-w_curswant = curwin-w_virtcol;
+ curwin-w_set_curswant = FALSE;
#if defined(FEAT_LINEBREAK) || defined(FEAT_MBYTE)
if (curwin-w_cursor.col 0 curwin-w_p_wrap)
{
***
*** 8228,8234
* the end of the line. We do not want to advance to
* the next screen line.
*/
- validate_virtcol();
if (curwin-w_virtcol (colnr_T)i)
--curwin-w_cursor.col;
}
--- 8233,8238
*** ../vim-7.4a.006/src/version.c 2013-07-09 14:58:06.0 +0200
--- src/version.c 2013-07-09 16:54:29.0 +0200
***
*** 730,731
--- 730,733
{ /* Add new patch number below this line */
+ /**/
+ 7,
/**/
--
JOHN CLEESE PLAYED: SECOND SOLDIER WITH A KEEN INTEREST IN BIRDS, LARGE MAN
WITH DEAD BODY, BLACK KNIGHT, MR NEWT (A VILLAGE
BLACKSMITH INTERESTED IN BURNING WITCHES), A QUITE
EXTRAORDINARILY RUDE FRENCHMAN, TIM THE WIZARD, SIR
LAUNCELOT
Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Patch 7.4a.006
Taro Muraoka wrote: After this patch, build was failed like this Mismatching error/warning code in line 3006 make[2]: *** [nl.ck] Error 1 make[2]: Leaving directory `/home/travis/build/vim-jp/vim-ci/vim/src/po' make[1]: *** [test] Error 2 Check this for details: https://travis-ci.org/vim-jp/vim-ci/jobs/8886799 Which is correct, the nl.po file contains errors. I pushed the corrected version to Mercurial. The error went unnoticed for a long time, since make just continued after reporting the error. -- TERRY GILLIAM PLAYED: PATSY (ARTHUR'S TRUSTY STEED), THE GREEN KNIGHT SOOTHSAYER, BRIDGEKEEPER, SIR GAWAIN (THE FIRST TO BE KILLED BY THE RABBIT) Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Patch 7.4a.008
Patch 7.4a.008
Problem:Python 3 doesn't handle multibyte characters prooperly when
'encoding' is not utf-8.
Solution: Use PyUnicode_Decode() instead of PyUnicode_FromString(). (Ken
Takata)
Files: src/if_python3.c
*** ../vim-7.4a.007/src/if_python3.c2013-07-03 18:27:35.0 +0200
--- src/if_python3.c2013-07-09 17:23:11.0 +0200
***
*** 86,92
#ifndef PyString_Check
# define PyString_Check(obj) PyUnicode_Check(obj)
#endif
! #define PyString_FromString(repr) PyUnicode_FromString(repr)
#define PyString_FromFormat PyUnicode_FromFormat
#ifndef PyInt_Check
# define PyInt_Check(obj) PyLong_Check(obj)
--- 86,93
#ifndef PyString_Check
# define PyString_Check(obj) PyUnicode_Check(obj)
#endif
! #define PyString_FromString(repr) \
! PyUnicode_Decode(repr, STRLEN(repr), ENC_OPT, NULL)
#define PyString_FromFormat PyUnicode_FromFormat
#ifndef PyInt_Check
# define PyInt_Check(obj) PyLong_Check(obj)
*** ../vim-7.4a.007/src/version.c 2013-07-09 17:08:24.0 +0200
--- src/version.c 2013-07-09 17:24:31.0 +0200
***
*** 730,731
--- 730,733
{ /* Add new patch number below this line */
+ /**/
+ 8,
/**/
--
MICHAEL PALIN PLAYED: 1ST SOLDIER WITH A KEEN INTEREST IN BIRDS, DENNIS, MR
DUCK (A VILLAGE CARPENTER WHO IS ALMOST KEENER THAN
ANYONE ELSE TO BURN WITCHES), THREE-HEADED KNIGHT, SIR
GALAHAD, KING OF SWAMP CASTLE, BROTHER MAYNARD'S ROOMATE
Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [patch][7.4a] :py3 vim.eval() doesn't handle multibyte characters properly
Ken Takata wrote:
:py3 vim.eval() doesn't handle multibyte characters properly
when 'encoding' is not utf-8 (e.g. cp932).
How to reproduce:
:set enc=cp932
:call setline(1, \u82a0) Set Hiragana Letter A 'あ' (U+3042 in Unicode)
:py3 import vim
:py3 print(vim.eval('getline(1)')) Printing 'あ' is expected.
Traceback (most recent call last):
File string, line 1, in module
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x82 in position 0:
invalid start byte
Attached patch fixes this problem.
Please check it.
Thanks, I'll include it.
--
Communication is one of the most compli..., eh, well, it's hard.
You know what I mean. Not?
/// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Breaking undo in Insert mode
Ben Fritz wrote: On Tue, Jul 9, 2013 at 5:54 AM, Bram Moolenaar b...@moolenaar.net wrote: That can be done by returning cursor key sequences. No need for setline(): imap ( C-R=LeftParen()CR fun! LeftParen() return ()\Left endfun imap ) C-R=RightParen()CR fun! RightParen() return \Right endfun I don't remember how setline() solves the problem, but just returning cursor sequences doesn't work, because it breaks undo/redo/repeat. Yeah, that's true. I suppose we could avoid saving for undo under certain conditions, but it's quite hard to decide what those conditions are. Perhaps when inserting a register and the cursor remains within the inserted text? If I insert abc(123) with mappings like, then press '.' somewhere else, I will only get the 123 inserted. Pressing 'u' after inserting abc(123) + 456 will only undo the + 456. The mappings that used to work to get around this are complicated; hence the reason I'm using a plugin instead of simple mappings; but previously somehow using setline() allowed all of undo, redo, and repeat to work as if there were not any mappings. Now only repeat works. -- I love deadlines. I especially like the whooshing sound they make as they go flying by. -- Douglas Adams /// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Patch 7.4a.009
Patch 7.4a.009
Problem:Compiler warnings for function prototypes.
Solution: Add void. Move list_features() prototype. (Ken Takata)
Files: src/gui_w48.c, src/if_py_both.h, src/version.c
*** ../vim-7.4a.008/src/gui_w48.c 2013-06-17 22:22:49.0 +0200
--- src/gui_w48.c 2013-07-09 17:38:08.0 +0200
***
*** 3102,3108
* 'guifont'
*/
static void
! update_im_font()
{
LOGFONT lf_wide;
--- 3102,3108
* 'guifont'
*/
static void
! update_im_font(void)
{
LOGFONT lf_wide;
*** ../vim-7.4a.008/src/if_py_both.h2013-07-06 12:57:36.0 +0200
--- src/if_py_both.h2013-07-09 17:38:08.0 +0200
***
*** 2100,2106
}
static list_T *
! py_list_alloc()
{
list_T*ret;
--- 2100,2106
}
static list_T *
! py_list_alloc(void)
{
list_T*ret;
***
*** 5857,5863
return -1;
static int
! init_types()
{
PYTYPE_READY(IterType);
PYTYPE_READY(BufferType);
--- 5857,5863
return -1;
static int
! init_types(void)
{
PYTYPE_READY(IterType);
PYTYPE_READY(BufferType);
*** ../vim-7.4a.008/src/version.c 2013-07-09 17:30:48.0 +0200
--- src/version.c 2013-07-09 17:39:20.0 +0200
***
*** 35,42
char longVersion[sizeof(VIM_VERSION_LONG_DATE) + sizeof(__DATE__)
+ sizeof(__TIME__) + 3];
- static void list_features __ARGS((void));
-
void
make_version()
{
--- 35,40
***
*** 57,62
--- 55,61
char *longVersion = VIM_VERSION_LONG;
#endif
+ static void list_features __ARGS((void));
static void version_msg __ARGS((char *s));
static char *(features[]) =
*** ../vim-7.4a.008/src/version.c 2013-07-09 17:30:48.0 +0200
--- src/version.c 2013-07-09 17:39:20.0 +0200
***
*** 730,731
--- 729,732
{ /* Add new patch number below this line */
+ /**/
+ 9,
/**/
--
The MS-Windows registry is no more hostile than any other bunch of state
information... that is held in a binary format... a format that nobody
understands... and is replicated and cached in a complex and largely
undocumented way... and contains large amounts of duplicate and obfuscated
information... (Ben Peterson)
/// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Patch] Fix Python indentation with trailing TODO comments
Chris Morgan wrote: File: runtime/indent/python.vim When checking for a colon at the end of a statement to decide whether to indent the next line, it strips trailing comments; however, the syntax group can be pythonTodo rather than pythonComment, which it was not detecting. Thus, a line like this: if True: # TODO would lead to the next line not being indented an extra level, which is not correct. The simple solution (employed here) is to change the check for `Comment$` to `(Comment|Todo)$`. A more complex but more-correct-in-case-of-user-extensions-to-the-syntax solution would check the whole synstack, but I deemed that as probably unnecessary. I'm happy to write such a thing if desired, though. This has been an issue for quite some time, probably since the beginning of that syntax file. Looks like a good solution. Thanks, I'll include it. -- Every time I lose weight, it finds me again! /// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Patch 7.4a.006
Yasuhiro Matsumoto wrote: How about sending e-mail contains compile error to vim-dev from travis-ci? I rather have a human look at the message first to avoid false alarms. If it's a real problem it should be easy to forward to vim-dev. Unless you can automatically generate a patch to fix the problem :-). -- Corn oil comes from corn and olive oil comes from olives, so where does baby oil come from? /// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Vim 7.4a ready for beta testing
On Tue, Jul 9, 2013 at 4:22 PM, Yukihiro Nakadaira yukihiro.nakada...@gmail.com wrote: On Tue, Jul 9, 2013 at 1:06 AM, glts 676c7...@gmail.com wrote: On Saturday, July 6, 2013 3:59:06 PM UTC+2, 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 documentation or a missing file. What was the last word on test86? It fails for me on Ubuntu 12.04 with 7.4a and --enable-pythoninterp. But that is expected, or is it not? And there is no workaround to make it green for the release? Easy workaround is using -fPIC or -fPIE. $ CFLAGS=-fPIE ./configure --enable-pythoninterp=yes make test Indeed. I don't understand the consequences but this makes the test pass. Thanks. -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [NFA] Slow Regexp with many branches
Nikolay Pavlov wrote:
On Jul 9, 2013 4:58 PM, Bram Moolenaar b...@moolenaar.net wrote:
Grüner_Gimpel wrote:
I noticed that using Vim 7.4a the Vimwiki plugin works measurably
slower with re=0 than with re=1. I figured out the reason is this
regexp in the syntax definition:
[[:alnum:]]\@!\%(\%(\%(http\|https\|file\|ftp\|gopher\|telnet\|nntp\|ldap\|rsync\|imap\|pop\|irc\|ircs\|cvs\|svn\|svn+ssh\|git\|ssh\|fish\|sftp\):\%(\/\/\)\)\|\%(mailto\|news\|xmpp\|sip\|sips\|doi\|urn\|tel\):\)\S\{-1,}\%(([^
\t()]*)\)\=\S*
You may know what it is supposed to match.
Removing some of the branches makes it faster and so does removing
[[:alnum:]]\@!
I don't know if there is a standard method for measuring speed of the
syntax highlight, but here is what I have done:
- open a relatively large file
- :set syn=off
- :syntax match Number
/[[:alnum:]]\@!\%(\%(\%(http\|https\|file\|ftp\|gopher\|telnet\|nntp\|ldap\|rsync\|imap\|pop\|irc\|ircs\|cvs\|svn\|svn+ssh\|git\|ssh\|fish\|sftp\):\%(\/\/\)\)\|\%(mailto\|news\|xmpp\|sip\|sips\|doi\|urn\|tel\):\)\S\{-1,}\%(([^
\t()]*)\)\=\S*/
- scroll with c-e and c-y
- extremely slow with re=0 but normal slow (*wink*) with re=1
So, can this behavior be considered as a bug?
The main problem is the [[:alnum:]]\@! item. Have you tried adding a
limit? Should be [[:alnum:]]\@1!
Or perhaps using \ instead will work.
For measuring times: use :syntime.
Could not it deduce a limit by itself in such simple cases?
In this case the [[:alnum:]]\@! is likely to be the root cause
as was already said.
However, alternative with \| are also costly because as far
as I know, the regexp engine has to either backtrack (with
old engine, re=1) or look for all alternatives at the same
time (with new engine, re=0).
I wonder: does the regexp engine attempts to simplify regexps
with alternatives? I'm thinking about this kind of optimizations:
https\|http--https\=
svn+ssh\|svn -- svn\%(+ssh\)\=
So at least the common prefix is checked only once in the new
engine. And with the old engine, there is no backtracking when
matching fails already in the common prefix.
Regards
Dominique
--
--
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Patch 7.4a.010
Patch 7.4a.010
Problem:Test 86 and 97 fail when building with Python or Python 3 and
using a static library.
Solution: Add configure check to add -fPIE compiler flag.
Files: src/configure.in, src/auto/configure
*** ../vim-7.4a.009/src/configure.in2013-07-03 19:25:28.0 +0200
--- src/configure.in2013-07-09 21:54:12.0 +0200
***
*** 1353,1364
--- 1353,1396
PYTHON_OBJ=objects/if_python.o
PYTHON_CFLAGS=$PYTHON_CFLAGS
-DDYNAMIC_PYTHON_DLL=\\\${python_INSTSONAME}\\\
PYTHON_LIBS=
+ elif test $python_ok = yes; then
+ dnl Check that adding -fPIE works. It may be needed when using a static
+ dnl Python library.
+ AC_MSG_CHECKING([if -fPIE can be added for Python])
+ cflags_save=$CFLAGS
+ libs_save=$LIBS
+ CFLAGS=$CFLAGS $PYTHON_CFLAGS -fPIE
+ LIBS=$LIBS $PYTHON_LIBS
+ AC_TRY_LINK(,[ ],
+AC_MSG_RESULT(yes); fpie_ok=yes,
+AC_MSG_RESULT(no); fpie_ok=no)
+ CFLAGS=$cflags_save
+ LIBS=$libs_save
+ if test $fpie_ok = yes; then
+ PYTHON_CFLAGS=$PYTHON_CFLAGS -fPIE
+ fi
elif test $python3_ok = yes test $enable_python3interp = dynamic;
then
AC_DEFINE(DYNAMIC_PYTHON3)
PYTHON3_SRC=if_python3.c
PYTHON3_OBJ=objects/if_python3.o
PYTHON3_CFLAGS=$PYTHON3_CFLAGS
-DDYNAMIC_PYTHON3_DLL=\\\${python3_INSTSONAME}\\\
PYTHON3_LIBS=
+ elif test $python3_ok = yes; then
+ dnl Check that adding -fPIE works. It may be needed when using a static
+ dnl Python library.
+ AC_MSG_CHECKING([if -fPIE can be added for Python3])
+ cflags_save=$CFLAGS
+ libs_save=$LIBS
+ CFLAGS=$CFLAGS $PYTHON3_CFLAGS -fPIE
+ LIBS=$LIBS $PYTHON3_LIBS
+ AC_TRY_LINK(,[ ],
+AC_MSG_RESULT(yes); fpie_ok=yes,
+AC_MSG_RESULT(no); fpie_ok=no)
+ CFLAGS=$cflags_save
+ LIBS=$libs_save
+ if test $fpie_ok = yes; then
+ PYTHON3_CFLAGS=$PYTHON3_CFLAGS -fPIE
+ fi
fi
AC_MSG_CHECKING(--enable-tclinterp argument)
*** ../vim-7.4a.009/src/auto/configure 2013-07-03 19:25:34.0 +0200
--- src/auto/configure 2013-07-09 21:54:15.0 +0200
***
*** 5991,5996
--- 5991,6028
PYTHON_OBJ=objects/if_python.o
PYTHON_CFLAGS=$PYTHON_CFLAGS
-DDYNAMIC_PYTHON_DLL=\\\${python_INSTSONAME}\\\
PYTHON_LIBS=
+ elif test $python_ok = yes; then
+ { $as_echo $as_me:${as_lineno-$LINENO}: checking if -fPIE can be added
for Python 5
+ $as_echo_n checking if -fPIE can be added for Python... 6; }
+ cflags_save=$CFLAGS
+ libs_save=$LIBS
+ CFLAGS=$CFLAGS $PYTHON_CFLAGS -fPIE
+ LIBS=$LIBS $PYTHON_LIBS
+ cat confdefs.h - _ACEOF conftest.$ac_ext
+ /* end confdefs.h. */
+
+ int
+ main ()
+ {
+
+ ;
+ return 0;
+ }
+ _ACEOF
+ if ac_fn_c_try_link $LINENO; then :
+ { $as_echo $as_me:${as_lineno-$LINENO}: result: yes 5
+ $as_echo yes 6; }; fpie_ok=yes
+ else
+ { $as_echo $as_me:${as_lineno-$LINENO}: result: no 5
+ $as_echo no 6; }; fpie_ok=no
+ fi
+ rm -f core conftest.err conftest.$ac_objext \
+ conftest$ac_exeext conftest.$ac_ext
+ CFLAGS=$cflags_save
+ LIBS=$libs_save
+ if test $fpie_ok = yes; then
+ PYTHON_CFLAGS=$PYTHON_CFLAGS -fPIE
+ fi
elif test $python3_ok = yes test $enable_python3interp = dynamic;
then
$as_echo #define DYNAMIC_PYTHON3 1 confdefs.h
***
*** 5998,6003
--- 6030,6067
PYTHON3_OBJ=objects/if_python3.o
PYTHON3_CFLAGS=$PYTHON3_CFLAGS
-DDYNAMIC_PYTHON3_DLL=\\\${python3_INSTSONAME}\\\
PYTHON3_LIBS=
+ elif test $python3_ok = yes; then
+ { $as_echo $as_me:${as_lineno-$LINENO}: checking if -fPIE can be added
for Python3 5
+ $as_echo_n checking if -fPIE can be added for Python3... 6; }
+ cflags_save=$CFLAGS
+ libs_save=$LIBS
+ CFLAGS=$CFLAGS $PYTHON3_CFLAGS -fPIE
+ LIBS=$LIBS $PYTHON3_LIBS
+ cat confdefs.h - _ACEOF conftest.$ac_ext
+ /* end confdefs.h. */
+
+ int
+ main ()
+ {
+
+ ;
+ return 0;
+ }
+ _ACEOF
+ if ac_fn_c_try_link $LINENO; then :
+ { $as_echo $as_me:${as_lineno-$LINENO}: result: yes 5
+ $as_echo yes 6; }; fpie_ok=yes
+ else
+ { $as_echo $as_me:${as_lineno-$LINENO}: result: no 5
+ $as_echo no 6; }; fpie_ok=no
+ fi
+ rm -f core conftest.err conftest.$ac_objext \
+ conftest$ac_exeext conftest.$ac_ext
+ CFLAGS=$cflags_save
+ LIBS=$libs_save
+ if test $fpie_ok = yes; then
+ PYTHON3_CFLAGS=$PYTHON3_CFLAGS -fPIE
+ fi
fi
{ $as_echo $as_me:${as_lineno-$LINENO}: checking --enable-tclinterp
argument 5
*** ../vim-7.4a.009/src/version.c 2013-07-09 17:42:42.0 +0200
--- src/version.c 2013-07-09 21:56:54.0 +0200
***
*** 729,730
--- 729,732
{ /* Add new patch number below this line */
+ /**/
+ 10,
/**/
--
(letter from Mark to Mike, about the film's probable certificate)
For an 'A' we would have to: Lose as many shits as possible; Take Jesus
Christ out, if possible; Loose I fart in your general direction; Lose
the oral sex; Lose oh, fuck off; Lose We make
Re: [NFA] Slow Regexp with many branches
Dominique pelle wrote:
Nikolay Pavlov wrote:
On Jul 9, 2013 4:58 PM, Bram Moolenaar b...@moolenaar.net wrote:
Grüner_Gimpel wrote:
I noticed that using Vim 7.4a the Vimwiki plugin works measurably
slower with re=0 than with re=1. I figured out the reason is this
regexp in the syntax definition:
[[:alnum:]]\@!\%(\%(\%(http\|https\|file\|ftp\|gopher\|telnet\|nntp\|ldap\|rsync\|imap\|pop\|irc\|ircs\|cvs\|svn\|svn+ssh\|git\|ssh\|fish\|sftp\):\%(\/\/\)\)\|\%(mailto\|news\|xmpp\|sip\|sips\|doi\|urn\|tel\):\)\S\{-1,}\%(([^
\t()]*)\)\=\S*
You may know what it is supposed to match.
Removing some of the branches makes it faster and so does removing
[[:alnum:]]\@!
I don't know if there is a standard method for measuring speed of the
syntax highlight, but here is what I have done:
- open a relatively large file
- :set syn=off
- :syntax match Number
/[[:alnum:]]\@!\%(\%(\%(http\|https\|file\|ftp\|gopher\|telnet\|nntp\|ldap\|rsync\|imap\|pop\|irc\|ircs\|cvs\|svn\|svn+ssh\|git\|ssh\|fish\|sftp\):\%(\/\/\)\)\|\%(mailto\|news\|xmpp\|sip\|sips\|doi\|urn\|tel\):\)\S\{-1,}\%(([^
\t()]*)\)\=\S*/
- scroll with c-e and c-y
- extremely slow with re=0 but normal slow (*wink*) with re=1
So, can this behavior be considered as a bug?
The main problem is the [[:alnum:]]\@! item. Have you tried adding a
limit? Should be [[:alnum:]]\@1!
Or perhaps using \ instead will work.
For measuring times: use :syntime.
Could not it deduce a limit by itself in such simple cases?
In this case the [[:alnum:]]\@! is likely to be the root cause
as was already said.
However, alternative with \| are also costly because as far
as I know, the regexp engine has to either backtrack (with
old engine, re=1) or look for all alternatives at the same
time (with new engine, re=0).
I wonder: does the regexp engine attempts to simplify regexps
with alternatives? I'm thinking about this kind of optimizations:
https\|http--https\=
svn+ssh\|svn -- svn\%(+ssh\)\=
So at least the common prefix is checked only once in the new
engine. And with the old engine, there is no backtracking when
matching fails already in the common prefix.
No, the new engine does not find common substrings. It would help to
implement this, pushing alternatives on the state list is consuming a
lot of the time. Anyone feel like looking into this?
--
Did Adam and Eve have navels?
/// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[patch] use correct python3 config directory when sys.abiflags is empty
Hi,
I've attached a patch to fix an issue where the wrong python3 config
directory is used when a system's sys.abiflags are empty.
Thanks,
Tim
--
--
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
# HG changeset patch
# User Tim Harder radher...@gmail.com
# Date 1373407408 25200
# Tue Jul 09 15:03:28 2013 -0700
# Node ID ce2cfb2b919ce460a3f9094c12013c2a1963b9ab
# Parent 5bb04d03dfa843c1080ed3872daacc42caa86542
Use correct python3 config directory when sys.abiflags is empty
diff -r 5bb04d03dfa8 -r ce2cfb2b919c src/configure.in
--- a/src/configure.in Tue Jul 09 21:57:52 2013 +0200
+++ b/src/configure.in Tue Jul 09 15:03:28 2013 -0700
@@ -1110,9 +1110,9 @@
AC_CACHE_CHECK(Python's configuration directory,vi_cv_path_python3_conf,
[
vi_cv_path_python3_conf=
- config_dir=config
+ config_dir=config-${vi_cv_var_python3_version}
if test ${vi_cv_var_python3_abiflags} != ; then
- config_dir=${config_dir}-${vi_cv_var_python3_version}${vi_cv_var_python3_abiflags}
+ config_dir=${config_dir}${vi_cv_var_python3_abiflags}
fi
d=`${vi_cv_path_python3} -c import distutils.sysconfig; print(distutils.sysconfig.get_config_var('LIBPL'))`
if test -d $d test -f $d/config.c; then
E315 errors in Vim 74a (folding, Python, buffers)
I get E315 errors in Vim 7.4a, but not in Vim 7.3.829 and earlier.
In a nutshell, when a buffer in another window is modified via Python
buffer object, folds in the current buffer get messed up, jumping to
the last line results in multiple E315.
The script below shows how to reproduce (also attached).
Specs: gVim 7.4a BETA (extracted from Windows installer, not
installed), Windows 8 64-bit, Python 2.7.5, Python 3.3.2. (I did not
test this with Python 3 because dll versions don't match.)
---BEGIN---
Create buffer 1 with closed folds.
tabnew Buffer1
call setline(1, ['','aaa {{{1','bbb {{{2','ccc {{{3'])
setl fdm=marker fdt=getline(v:foldstart) fdl=0
Create buffer 2 in another window.
new Buffer2
py import vim
py B2=vim.current.buffer
Go back to buffer 1. Modify buffer 2 via Python.
wincmd w
This alone messes up folding in the current buffer.
py B2.append(['xxx','yyy'])
This results in multiple 'E315: ml_get: invalid lnum: 6'.
A spurious window appears sometimes.
Custom statusline and tabline are also disrupted.
normal! ggVG
---END---
--
--
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
vim74a_E315.vim
Description: Binary data
Re: Vim 7.4a ready for beta testing (test96 FAILED)
Bram Moolenaar wrote: Raf wrote: 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 documentation or a missing file. mid-2010 macbookpro macosx-10.6.8 gcc-4.2.1 obtained vim-7.4a.002 via hg (same result via ftp). configure \ --disable-darwin \ --with-x \ --enable-gui=motif \ --enable-multibyte \ --with-mac-arch=current \ --with-features=huge \ --disable-acl Test results: test96 FAILED TEST FAILURE diff -u test96.ok test96.failed --- test96.ok 2013-07-08 10:12:36.0 +1000 +++ test96.failed 2013-07-08 10:15:31.0 +1000 @@ -4,6 +4,8 @@ - quickfix claims that the file name displayed is: test://bar.txt Test B: - number of window open: 2 +Test B: + - number of window open: 2 Test C: - 'buftype' of the location list window: quickfix - buffer displayed in the 2nd window: test://quux.txt i.e. the Test B section of the file is repeated. That's strange. Please check that your version of src/testdir/test96.in is the same as https://code.google.com/p/vim/source/browse/src/testdir/test96.in it's the same. MD5 (/usr/local/src/vim74/src/testdir/test96.in) = 3222973df5598f7ff3297d3cf9b5ecd9 i've tried with three separate copies of 7.4a.010: hg (https://vim.googlecode.com/hg/) test96 fails hg (https://code.google.com/p/vim) test96 fails ftp (ftp.vim.org) test96 passes how wierd is that? the two hg versions are the same but there are some differences between them and the ftp version. the differences are that the ftp version has older versions of: Makefile runtime/compiler/checkstyle.vim runtime/compiler/javac.vim runtime/compiler/php.vim runtime/compiler/se.vim runtime/compiler/tcl.vim runtime/compiler/tidy.vim runtime/compiler/xmllint.vim runtime/doc/diff.txt runtime/doc/options.txt runtime/doc/todo.txt runtime/doc/uganda.txt runtime/doc/version7.txt runtime/plugin/tohtml.vim runtime/synmenu.vim runtime/syntax/2html.vim runtime/syntax/help.vim src/po/nl.po src/po/pl.UTF-8.po src/po/pl.cp1250.po src/po/pl.po src/po/ru.cp1251.po src/po/ru.po i don't know if that helps. the actual diff can be found at http://raf.org/tmp/vim74a.010-ftp-v-code.google.com-p-vim.diff if it's of any use. it's odd that yesterday the ftp version of 7.4a.002 failed but today the ftp version of 7.4a.010 passed. i just tested the ftp version again at every patchlevel up to 010 and they all worked. the hg version still fails though. bizarre. cheers, raf -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Vim didn't load my user scripts after upgraded to 7.4a from 7.3.1311
It's wired. Did we make any big change between these revisions? My system: Windows 7 with sp1. Before my upgrade, my Vim installed to D:\Apps\Vim with following directory structure: D:\Apps\Vim vim73\ vim 7.3.1311 vimfiles\my plugins/colors, etc. _vimrc everything works well. But after my upgrade, vim failed to load every scripts in vimfiles, neither plugin nor colors, everything in it. I dont's understand for why? I thought that should rename vim73 to vim74, as what I've done for upgrade vim 7.2 to 7.3, but it didn't works. Now I open my gVim.exe, it shows me just like a fresh install: no customization, default color scheme, etc. Is it a bug or some sort of new features? -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
