Loading ...
Sorry, an error occurred while loading the content.

1031Re: yanking linewise

Expand Messages
  • Ben Fowler
    Jul 2, 2003
    • 0 Attachment
      At 12:28 pm -0400 2003-07-01, Ricardo SIGNES wrote:
      >* Ben Fowler <bfowler@...> [2003-07-01T12:06:19]
      >> At 11:41 am -0400 2003-07-01, Ricardo SIGNES wrote:
      >> > [ bug report ]
      >> Which is the correct behaviour? I assume the former.
      >The correct behaviour -- found in gVim and Vim on Win32 and GNU/Linux
      >(with and without X11) is the former -- the linewise-yanked line is
      >inserted as its own line below the line on which the cursor sits.
      >> When I tried to reproduce this with a recent version:
      >> ~ VIM - Vi IMproved
      >> ~ version 6.2.14
      >Were you using the version from http://macvim.swdev.org/OSX? It is
      >identified in :ver as "Huge version with Carbon GUI"

      No, I am using one that I compiled myself.

      :ver gives me

      VIM - Vi IMproved 6.2 (2003 Jun 1, compiled 06/14/03 00:58:48)
      Included patches: 1-14
      Compiled by bfowler@...
      Normal version with X11-Athena GUI. Features included (+) or not (-):
      -arabic +autocmd +balloon_eval +browse +builtin_terms +byte_offset +cindent +clientserver +clipboard
      +cmdline_compl +cmdline_hist +cmdline_info +comments +cryptv -cscope +dialog_con_gui +diff +digraphs -dnd
      -ebcdic -emacs_tags +eval +ex_extra +extra_search -farsi +file_in_path +find_in_path +folding -footer
      +fork() -gettext -hangul_input -iconv +insert_expand +jumplist -keymap -langmap -libcall +linebreak
      +lispindent +listcmds +localmap +menu +mksession +modify_fname +mouse +mouseshape -mouse_dec -mouse_gpm
      -mouse_jsbterm -mouse_netterm +mouse_xterm -multi_byte +multi_lang -netbeans_intg -osfiletype +path_extra
      -perl +postscript +printer -python +quickfix -rightleft -ruby +scrollbind -signs +smartindent -sniff
      +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
      system vimrc file: "$VIM/vimrc"
      user vimrc file: "$HOME/.vimrc"
      user exrc file: "$HOME/.exrc"
      system gvimrc file: "$VIM/gvimrc"
      user gvimrc file: "$HOME/.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_ATHENA -g -O2 -fno-strength-reduce -I/usr/
      gcc -L/usr/X11R6/lib -L/usr/local/lib -o vim -lXaw -lXmu -lXext -lXpm -lXt -lX11 -lncurses
      Hit ENTER or type command to continue

      I ran 'configure' before compiling my Vim with the .pbproj . Perhaps there is something
      in the may that my compilation was done that hides this bug.

      > > I got the former (id est correct) behaviour both times.
      > > I enclose my 'bugreport.vim' result.
      >I don't see any enclosed file... do I misunderstand?

      Another copy ...
    • Show all 25 messages in this topic