Comment #3 on issue 150 by [email protected]: same normal cmds on linux
and windows
http://code.google.com/p/vim/issues/detail?id=150
I tested with vim 7.3.822 on win7 this config:
:ver
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jul 17 2013 03:39:13)
MS-Windows 32-bit console version
Included patches: 1-822
Compiled by g_user7@win7-PC
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 -gettext -hangul_input +iconv/dyn
+insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent
+listcmds
+localmap -lua +menu +mksession +modify_fname +mouse -mouseshape
+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
-tgetent -termresponse +textobjects +title -toolbar +user_commands
+vertsplit
+virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu
+windows +writebackup -xfontset -xim -xterm_save -xpm_w32
system vimrc file: "$VIM\vimrc"
user vimrc file: "$HOME\_vimrc"
2nd 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 -DFEAT_MBYTE -DDYNAMIC_ICONV -DFEAT_HUGE /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 /ma
chine:i386 /nodefaultlib libcmt.lib user32.lib /PDB:vim.pdb
-debug
vimrc file used:
" http://vimdoc.sourceforge.net/htmldoc/starting.html#vimrc
set nocompatible " use vim defaults
set scrolloff=3 " keep 3 lines when scrolling
set ai " set auto-indenting on for programming
set showcmd " display incomplete commands
set nobackup " do not keep a backup file
set number " show line numbers
set ruler " show the current row and column
set hlsearch " highlight searches
set incsearch " do incremental searching
set showmatch " jump to matches when entering regexp
set ignorecase " ignore case when searching
set smartcase " no ignorecase if Uppercase char present
set visualbell t_vb= " turn off error beep/flash
set novisualbell " turn off visual bell
set backspace=indent,eol,start " make that backspace key work the way it
should
syntax on " turn syntax highlighting on by default
filetype on " detect type of file
filetype indent on " load indent file for specific file type
set t_RV= " http://bugs.debian.org/608242,
http://groups.google.com/group/vim_dev/browse_thread/thread/9770ea844cec3282
After executed the vim normal command on fileinwin32 input file:
:%no<S-Tab>!Y6r gw}Vp<CR>
with the config above, in last paragraph of buffer, the word "BL" is
repeated on the next line and "connotation" is pushed on next line.
Also, I used this line windows command to start vim:
vim -u NONE -U NONE fileinwin32
In this case the paragraphs are not indented, but word "BL," is added,
after execution of vim normal command, and the word "BL," appears two times.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
