Skip Menu |

This queue is for tickets about the Text-VimColor CPAN distribution.

Report information
The Basics
Id: 92601
Status: open
Priority: 0/
Queue: Text-VimColor

People
Owner: Nobody in particular
Requestors: RSAVAGE [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Critical
Broken in: 0.23
Fixed in: (no value)



Subject: Encoding test failures
Hi From the console log: t/000-vim-version.t .... ok t/ansi.t ............... ok t/bin.t ................ ok t/compare-formats.t .... ok # Failed test 'use BOM to get vim to honor encoded text (LANG=en_US.UTF-8)' # at t/encoding.t line 31. Wide character in print at /home/ron/perl5/perlbrew/perls/perl-5.14.2/lib/5.14.2/Test/Builder.pm line 1759. # got: '<span class="synSpecial">(</span><span class="synComment"> ��rl + </span><span class="synTodo">vim</span><span class="synComment"> </span><span class="synSpecial">)</span> # ' # expected: '<span class="synSpecial">(</span><span class="synComment"> þêrl + </span><span class="synTodo">vim</span><span class="synComment"> </span><span class="synSpecial">)</span> # ' # Failed test 'specify encoding by adding "+set fenc=..." to vim_options (LANG=en_US.UTF-8)' # at t/encoding.t line 31. # got: '<span class="synSpecial">(</span><span class="synComment"> þêrl + </span><span class="synTodo">vim</span><span class="synComment"> </span><span class="synSpecial">)</span> # ' # expected: '<span class="synSpecial">(</span><span class="synComment"> ��rl + </span><span class="synTodo">vim</span><span class="synComment"> </span><span class="synSpecial">)</span> # ' # Looks like you failed 2 tests of 19. t/encoding.t ........... Dubious, test returned 2 (wstat 512, 0x200) Failed 2/19 subtests t/html.t ............... ok t/input_filename.t ..... ok t/new.t ................ ok t/override-options.t ... ok t/share-dir.t .......... ok t/tvctestsyn.t ......... ok t/untie-std-handles.t .. ok t/vim_let.t ............ ok t/vim_options.t ........ ok t/xml.t ................ ok Test Summary Report ------------------- t/encoding.t (Wstat: 512 Tests: 19 Failed: 2) Failed tests: 9-10 Non-zero exit status: 2 Files=17, Tests=146, 3 wallclock secs ( 0.08 usr 0.02 sys + 2.30 cusr 0.28 csys = 2.68 CPU) Result: FAIL Failed 1/17 test programs. 2/146 subtests failed.
Thanks. I've seen a few of those but haven't had a chance to look into it yet... I need to find an OS that exhibits the failure and create a vm for it. I think all the reports I've seen so far for this have been FreeBSD. What's your OS (and version)? Your default locale? Output of `vim --version`?
What's your default fileencodings setting? Do: `vim --cmd 'echo &fencs' --cmd q`
Subject: Re: [rt.cpan.org #92601] Encoding test failures
Date: Fri, 31 Jan 2014 14:15:05 +1100
To: bug-Text-VimColor [...] rt.cpan.org
From: Ron Savage <ron [...] savage.net.au>
Hi Randy On 31/01/14 13:42, Randy Stauner via RT wrote: Show quoted text
> `vim --version`
VIM - Vi IMproved ~ ~ version 7.3.547 -- Ron Savage http://savage.net.au/
Subject: Re: [rt.cpan.org #92601] Encoding test failures
Date: Fri, 31 Jan 2014 14:17:01 +1100
To: bug-Text-VimColor [...] rt.cpan.org
From: Ron Savage <ron [...] savage.net.au>
Hi Randy On 31/01/14 13:46, Randy Stauner via RT wrote: Show quoted text
> `vim --cmd 'echo &fencs' --cmd q`
ron@zigzag:~/Documents/repos$ `vim --cmd 'echo &fencs' --cmd q` Vim: Warning: Output is not to a terminal ucs-bom,utf-8,default,latin1 -bash: $'\E[?25l\E[J\E[55;1H\E[?12l\E[?25h': command not found BTW I use UltraEdit, not vim. I'm also cleaning up Makefile.PL but an just going out for an hour or so. Stay tuned. -- Ron Savage http://savage.net.au/
Subject: Re: [rt.cpan.org #92601] Encoding test failures
Date: Fri, 31 Jan 2014 14:18:07 +1100
To: bug-Text-VimColor [...] rt.cpan.org
From: Ron Savage <ron [...] savage.net.au>
On 31/01/14 13:42, Randy Stauner via RT wrote: Sorry for the confusion. Forget the Makefile.PL reference. That's Shell::Perl. I'm using Debian V 7. -- Ron Savage http://savage.net.au/
Show quoted text
> BTW I use UltraEdit, not vim.
This module uses `vim` for its functionality. UltraEdit doesn't replace vim, does it? Your 'vim' command is really vim, right? I was surprised by the terseness of your output... `vim --version` usually shows the list of compiled features and some settings: $ vim --version VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jan 29 2014 08:51:45) Compiled by rando@raptor Huge version with GTK2 GUI. Features included (+) or not (-): +arabic +file_in_path +mouse_sgr +tag_binary +autocmd +find_in_path -mouse_sysmouse +tag_old_static +balloon_eval +float +mouse_urxvt -tag_any_white +browse +folding +mouse_xterm -tcl ++builtin_terms -footer +multi_byte +terminfo +byte_offset +fork() +multi_lang +termresponse +cindent +gettext -mzscheme +textobjects +clientserver -hangul_input +netbeans_intg +title +clipboard +iconv +path_extra +toolbar +cmdline_compl +insert_expand +perl/dyn +user_commands +cmdline_hist +jumplist +persistent_undo +vertsplit +cmdline_info +keymap +postscript +virtualedit +comments +langmap +printer +visual +conceal +libcall +profile +visualextra +cryptv +linebreak +python/dyn +viminfo +cscope +lispindent +python3/dyn +vreplace +cursorbind +listcmds +quickfix +wildignore +cursorshape +localmap +reltime +wildmenu +dialog_con_gui -lua +rightleft +windows +diff +menu -ruby +writebackup +digraphs +mksession +scrollbind +X11 +dnd +modify_fname +signs -xfontset -ebcdic +mouse +smartindent +xim +emacs_tags +mouseshape -sniff +xsmp_interact +eval +mouse_dec +startuptime +xterm_clipboard +ex_extra -mouse_gpm +statusline -xterm_save +extra_search -mouse_jsbterm -sun_workshop +farsi +mouse_netterm +syntax system vimrc file: "$VIM/vimrc" user vimrc file: "$HOME/.vimrc" 2nd user vimrc file: "~/.vim/vimrc" user exrc file: "$HOME/.exrc" system gvimrc file: "$VIM/gvimrc" user gvimrc file: "$HOME/.gvimrc" 2nd user gvimrc file: "~/.vim/gvimrc" system menu file: "$VIMRUNTIME/menu.vim" fall-back for $VIM: "/usr/local/share/vim" Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/local/include -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 Linking: gcc -Wl,-E -L/usr/local/lib -Wl,--as-needed -o vim -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lglib-2.0 -lSM -lICE -lXt -lX11 -lXdmcp -lSM -lICE -lm -ltinfo -lnsl -ldl -Wl,-E -fstack-protector -L/usr/local/lib -L/usr/lib/perl/5.14/CORE -lperl -ldl -lm -lpthread -lcrypt It works on Debian 6, I can't imagine why it wouldn't work on Debian 7 by default. What's your locale? I haven't been able to reproduce the error by changing environment settings, and your 'fileencodings' setting seems appropriate. I continue to be stumped.
Subject: Re: [rt.cpan.org #92601] Encoding test failures
Date: Fri, 31 Jan 2014 16:17:41 +1100
To: bug-Text-VimColor [...] rt.cpan.org
From: Ron Savage <ron [...] savage.net.au>
Hi Randy No, UltraEdit does not emulate vi or vim, but does make them, and Emacs, redundant. This may explain more: ron@zigzag:~/Documents/repos$ vi --version VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Feb 10 2013 02:28:47) Included patches: 1-547 Modified by pkg-vim-maintainers@lists.alioth.debian.org Compiled by jamessan@debian.org Huge version without GUI. Features included (+) or not (-): +arabic +autocmd -balloon_eval -browse ++builtin_terms +byte_offset +cindent -clientserver -clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments +conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con +diff +digraphs -dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path +float +folding -footer +fork() +gettext -hangul_input +iconv +insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap -lua +menu +mksession +modify_fname +mouse -mouseshape +mouse_dec +mouse_gpm -mouse_jsbterm +mouse_netterm -mouse_sysmouse +mouse_xterm +mouse_urxvt +multi_byte +multi_lang -mzscheme +netbeans_intg +path_extra -perl +persistent_undo +postscript +printer +profile -python -python3 +quickfix +reltime +rightleft -ruby +scrollbind +signs +smartindent -sniff +startuptime +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title -toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup -X11 -xfontset -xim -xsmp -xterm_clipboard -xterm_save system vimrc file: "$VIM/vimrc" user vimrc file: "$HOME/.vimrc" user exrc file: "$HOME/.exrc" fall-back for $VIM: "/usr/share/vim" Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 Linking: gcc -Wl,-z,relro -Wl,--as-needed -o vim -lm -ltinfo -lnsl -lselinux -lacl -lattr -lgpm ron@zigzag:~/Documents/repos$ which vim /usr/bin/vim ron@zigzag:~/Documents/repos$ which vi /usr/bin/vi ron@zigzag:~/Documents/repos$ dir /usr/bin/vim /usr/bin/vi lrwxrwxrwx 1 root root 20 Jun 5 2013 /usr/bin/vi -> /etc/alternatives/vi* lrwxrwxrwx 1 root root 21 Jun 10 2013 /usr/bin/vim -> /etc/alternatives/vim* ron@zigzag:~/Documents/repos$ dir /etc/alternatives/vi* lrwxrwxrwx 1 root root 18 Jun 10 2013 /etc/alternatives/vi -> /usr/bin/vim.basic* lrwxrwxrwx 1 root root 18 Jun 10 2013 /etc/alternatives/vim -> /usr/bin/vim.basic* lrwxrwxrwx 1 root root 18 Jun 10 2013 /etc/alternatives/vimdiff -> /usr/bin/vim.basic* So vi and vim are the same executable. On 31/01/14 14:31, Randy Stauner via RT wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=92601 > > It works on Debian 6, I can't imagine why it wouldn't work on Debian 7 by default. What's your locale? > > I haven't been able to reproduce the error by changing environment settings, and your 'fileencodings' setting seems appropriate. > > I continue to be stumped.
ron@zigzag:~/Documents/repos$ env | grep LANG LANG=en_AU.UTF-8 LANGUAGE=en_AU:en -- Ron Savage http://savage.net.au/
More info: All this while trying to install Pod::Server. Since the latter run under Perl 5.14.2, it's the Perl 5.18.2 env which is the problem, I'd say.
I'm seeing the same failure under 64-bit Windows 7 with a fresh vim installed (version info pasted below). I went ahead and forced the install and everything actually works great - pretty sweet module that does exactly what I need. If you want me to test anything under Windows, just send it over - but if the same behavior is cropping up under Debian it sounds like (for ONCE in my life) Windows is not at fault. Michael VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Aug 10 2013 14:33:40) MS-Windows 32-bit console version Compiled by mool@tororo Big version without GUI. Features included (+) or not (-): +arabic +ex_extra -mouseshape +tag_binary +autocmd +extra_search +multi_byte +tag_old_static -balloon_eval +farsi +multi_lang -tag_any_white -browse +file_in_path -mzscheme -tcl ++builtin_terms +find_in_path -netbeans_intg -tgetent +byte_offset +float +path_extra -termresponse +cindent +folding -perl +textobjects +clientserver -footer +persistent_undo +title +clipboard +gettext/dyn -postscript -toolbar +cmdline_compl -hangul_input +printer +user_commands +cmdline_hist +iconv/dyn -profile +vertsplit +cmdline_info +insert_expand -python +virtualedit +comments +jumplist -python3 +visual +conceal +keymap +quickfix +visualextra +cryptv +langmap +reltime +viminfo +cscope +libcall +rightleft +vreplace +cursorbind +linebreak -ruby +wildignore +cursorshape +lispindent +scrollbind +wildmenu +dialog_con +listcmds +signs +windows +diff +localmap +smartindent +writebackup +digraphs -lua -sniff -xfontset -dnd +menu +startuptime -xim -ebcdic +mksession +statusline -xterm_save +emacs_tags +modify_fname -sun_workshop -xpm_w32 +eval +mouse +syntax system vimrc file: "$VIM\vimrc" user vimrc file: "$HOME\_vimrc" 2nd user vimrc file: "$HOME\vimfiles\vimrc" 3rd user vimrc file: "$VIM\_vimrc" user exrc file: "$HOME\_exrc" 2nd user exrc file: "$VIM\_exrc" Compilation: cl -c /W3 /nologo -I. -Iproto -DHAVE_PATHDEF -DWIN32 -DFEAT_CSCOPE -DWINVER=0x0400 -D_WIN32_WINNT=0x0400 /Fo.\ObjCi386/ /Ox /GL -DNDEBUG /Zl /MT -DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_BIG /Fd.\ObjCi386/ /Zi Linking: link /RELEASE /nologo /subsystem:console /LTCG:STATUS oldnames.lib kernel32.lib advapi32.lib shell32.lib gdi32.lib comdlg32.lib ole32.lib uuid.lib /machine:i386 /nodefaultlib libcmt.lib user32.lib /PDB:vim.pdb -debug
Oh, I should have added: Strawberry perl 5.14.2, MSWin32-x64-multi-thread - so it's not 5.18 that is the problem.
Thanks for the additional report. The problem is actually with the tests. The tests that sometimes fail are ones I specifically added to ensure that I didn't break backward compatibility for the way some other modules were using this one. Their usage doesn't appear to be entirely portable, but it apparently works for them. So I need to modify the tests to only perform those back-compat tests *if* the behavior *should* work in the current environment. In order to do that I started a major refactor (moving some logic out into another module), but unfortunately left that in an unfinished state. So for now I have made a new release marking those unportable tests as TODO's and hopefully I can get back to my refactoring some day so that I could actually determine *if* those tests should be run and then rely on the result. Thanks for the reports. If you get a chance to try out the new release let me know how it works for you.
Subject: Re: [rt.cpan.org #92601] Encoding test failures
Date: Mon, 14 Apr 2014 08:31:00 +1000
To: bug-Text-VimColor [...] rt.cpan.org
From: Ron Savage <ron [...] savage.net.au>
Hi Randy Thanx for the new version: ron@zigzag:~/backup$ cpanm Text::VimColor --> Working on Text::VimColor Fetching http://www.cpan.org/authors/id/R/RW/RWSTAUNER/Text-VimColor-0.24.tar.gz ... OK Configuring Text-VimColor-0.24 ... OK Building and testing Text-VimColor-0.24 ... OK Successfully installed Text-VimColor-0.24 1 distribution installed ron@zigzag:~/backup$ uname -a Linux zigzag 3.2.0-4-amd64 #1 SMP Debian 3.2.54-2 x86_64 GNU/Linux ron@zigzag:~/backup$ cat /etc/debian_version 7.4 Cheers On 14/04/14 04:21, Randy Stauner via RT wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=92601 > > > Thanks for the additional report. > > The problem is actually with the tests. > > The tests that sometimes fail are ones I specifically added to ensure that I didn't break backward compatibility for the way some other modules were using this one. > > Their usage doesn't appear to be entirely portable, > but it apparently works for them. > > So I need to modify the tests to only perform those back-compat tests *if* the behavior *should* work in the current environment. > > In order to do that I started a major refactor (moving some logic out into another module), but unfortunately left that in an unfinished state. > > So for now I have made a new release marking those unportable tests as TODO's and hopefully I can get back to my refactoring some day so that I could actually determine *if* those tests should be run and then rely on the result. > > Thanks for the reports. If you get a chance to try out the new release let me know how it works for you. >
-- Ron Savage savage.net.au