[gentoo-user] Commenting out multiple lines in vim

[gentoo-user] Commenting out multiple lines in vim

[Stroller]

Hi there,

I can find numerous references on the net to this behaviour:

    In vim, you can just select the rectangular region with Ctrl-v,
    then type "I#<ESC>".  This will insert # in each line at the same
    column.  Very convenient.

EG:
http://mail.python.org/pipermail/python-list/2001-May/084540.html
http://hurley.wordpress.com/2007/06/13/vim-tip-comment-out-multiple-lines/

Yet it doesn't seem to work on any of my Gentoo systems.

Is this something that is caused by a Gentoo-specific /etc/vimrc or  
has vim evolved?

Any comments gratefully received.

Stroller.

Re: [gentoo-user] Commenting out multiple lines in vim

[Alexander Pilipovsky]

[-- Attachment #1: Type: text/plain, Size: 6969 bytes --]

Stroller ???????(??):
> Hi there,
>
> I can find numerous references on the net to this behaviour:
>
>    In vim, you can just select the rectangular region with Ctrl-v,
>    then type "I#<ESC>".  This will insert # in each line at the same
>    column.  Very convenient.
>
> EG:
> http://mail.python.org/pipermail/python-list/2001-May/084540.html
> http://hurley.wordpress.com/2007/06/13/vim-tip-comment-out-multiple-lines/ 
>
>
> Yet it doesn't seem to work on any of my Gentoo systems.
>
> Is this something that is caused by a Gentoo-specific /etc/vimrc or 
> has vim evolved?
>
> Any comments gratefully received.
>
> Stroller.
>
>
Exuse me, but it works on my computer :) And thanks about this topic, I 
didn't know about this feature!

I selected region by Ctrl-v, pressed Shift-I and white selection 
disappeared, I pressed # and ESC and got this effect...
My vimrc:
scriptencoding utf-8
" ^^ Please leave the above line at the start of the file.

" Default configuration file for Vim
" $Header: /var/cvsroot/gentoo-x86/app-editors/vim-core/files/vimrc-r3,v 
1.1 2006/03/25 20:26:27 genstef Exp $

" Written by Aron Griffis <agriffis@gentoo.org>
" Modified by Ryan Phillips <rphillips@gentoo.org>
" Modified some more by Ciaran McCreesh <ciaranm@gentoo.org>
" Added Redhat's vimrc info by Seemant Kulleen <seemant@gentoo.org>

" You can override any of these settings on a global basis via the
" "/etc/vim/vimrc.local" file, and on a per-user basis via "~/.vimrc". 
You may
" need to create these.

" {{{ General settings
" The following are some sensible defaults for Vim for most users.
" We attempt to change as little as possible from Vim's defaults,
" deviating only where it makes sense
set nocompatible        " Use Vim defaults (much better!)
set bs=2                " Allow backspacing over everything in insert mode
set ai                  " Always set auto-indenting on
set history=50          " keep 50 lines of command history
set ruler               " Show the cursor position all the time

set viminfo='20,\"500   " Keep a .viminfo file.

" Don't use Ex mode, use Q for formatting
map Q gq

" When doing tab completion, give the following files lower priority. 
You may
" wish to set 'wildignore' to completely ignore files, and 'wildmenu' to 
enable
" enhanced tab completion. These can be done in the user vimrc file.
set suffixes+=.info,.aux,.log,.dvi,.bbl,.out,.o,.lo

" When displaying line numbers, don't use an annoyingly wide number 
column. This
" doesn't enable line numbers -- :set number will do that. The value 
given is a
" minimum width to use for the number column, not a fixed size.
if v:version >= 700
  set numberwidth=3
endif
" }}}

" {{{ Modeline settings
" We don't allow modelines by default. See bug #14088 and bug #73715.
" If you're not concerned about these, you can enable them on a per-user
" basis by adding "set modeline" to your ~/.vimrc file.
set nomodeline
" }}}

" {{{ Locale settings
" Try to come up with some nice sane GUI fonts. Also try to set a sensible
" value for fileencodings based upon locale. These can all be overridden in
" the user vimrc file.
if v:lang =~? "^ko"
  set fileencodings=euc-kr
  set guifontset=-*-*-medium-r-normal--16-*-*-*-*-*-*-*
elseif v:lang =~? "^ja_JP"
  set fileencodings=euc-jp
  set guifontset=-misc-fixed-medium-r-normal--14-*-*-*-*-*-*-*
elseif v:lang =~? "^zh_TW"
  set fileencodings=big5
  set 
guifontset=-sony-fixed-medium-r-normal--16-150-75-75-c-80-iso8859-1,-taipei-fixed-medium-r-normal--16-150-75-75-c-160-big5-0
elseif v:lang =~? "^zh_CN"
  set fileencodings=gb2312
  set guifontset=*-r-*
endif

" If we have a BOM, always honour that rather than trying to guess.
if &fileencodings !~? "ucs-bom"
  set fileencodings^=ucs-bom
endif

" Always check for UTF-8 when trying to determine encodings.
if &fileencodings !~? "utf-8"
  set fileencodings+=utf-8
endif

" Make sure we have a sane fallback for encoding detection
set fileencodings+=default
" }}}

" {{{ Syntax highlighting settings
" Switch syntax highlighting on, when the terminal has colors
" Also switch on highlighting the last used search pattern.
if &t_Co > 2 || has("gui_running")
  syntax on
  set hlsearch
endif
" }}}

" {{{ Terminal fixes
if &term ==? "xterm"
  set t_Sb=^[4%dm
  set t_Sf=^[3%dm
  set ttymouse=xterm2
endif

if &term ==? "gnome" && has("eval")
  " Set useful keys that vim doesn't discover via termcap but are in the
  " builtin xterm termcap. See bug #122562. We use exec to avoid having to
  " include raw escapes in the file.
  exec "set <C-Left>=\eO5D"
  exec "set <C-Right>=\eO5C"
endif
" }}}

" {{{ Filetype plugin settings
" Enable plugin-provided filetype settings, but only if the ftplugin
" directory exists (which it won't on livecds, for example).
if isdirectory(expand("$VIMRUNTIME/ftplugin"))
  filetype plugin on

  " Uncomment the next line (or copy to your ~/.vimrc) for plugin-provided
  " indent settings. Some people don't like these, so we won't turn them 
on by
  " default.
  " filetype indent on
endif
" }}}

" {{{ Fix &shell, see bug #101665.
if "" == &shell
  if executable("/bin/bash")
    set shell=/bin/bash
  elseif executable("/bin/sh")
    set shell=/bin/sh
  endif
endif
"}}}

" {{{ Our default /bin/sh is bash, not ksh, so syntax highlighting for .sh
" files should default to bash. See :help sh-syntax and bug #101819.
if has("eval")
  let is_bash=1
endif
" }}}

" {{{ Autocommands
if has("autocmd")

augroup gentoo
  au!

  " Gentoo-specific settings for ebuilds.  These are the federally-mandated
  " required tab settings.  See the following for more information:
  " http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml
  " Note that the rules below are very minimal and don't cover everything.
  " Better to emerge app-vim/gentoo-syntax, which provides full syntax,
  " filetype and indent settings for all things Gentoo.
  au BufRead,BufNewFile *.e{build,class} let is_bash=1|setfiletype sh
  au BufRead,BufNewFile *.e{build,class} set ts=4 sw=4 noexpandtab

  " In text files, limit the width of text to 78 characters, but be careful
  " that we don't override the user's setting.
  autocmd BufNewFile,BufRead *.txt
        \ if &tw == 0 && ! exists("g:leave_my_textwidth_alone") |
        \     setlocal textwidth=78 |
        \ endif

  " When editing a file, always jump to the last cursor position
  autocmd BufReadPost *
        \ if ! exists("g:leave_my_cursor_position_alone") |
        \     if line("'\"") > 0 && line ("'\"") <= line("$") |
        \         exe "normal g'\"" |
        \     endif |
        \ endif

  " When editing a crontab file, set backupcopy to yes rather than auto. See
  " :help crontab and bug #53437.
  autocmd FileType crontab set backupcopy=yes

augroup END

endif " has("autocmd")
" }}}

" {{{ vimrc.local
if filereadable("/etc/vim/vimrc.local")
  source /etc/vim/vimrc.local
endif
" }}}

" vim: set fenc=utf-8 tw=80 sw=2 sts=2 et foldmethod=marker :

-- 
Alexander Pilipovsky aka Engraver


[-- Attachment #2: Type: text/html, Size: 10029 bytes --]

Re: [gentoo-user] Commenting out multiple lines in vim

[Stroller]

On 12 Feb 2009, at 20:16, Alexander Pilipovsky wrote:
> Stroller написав(ла):
>>
>> Hi there,
>>
>> I can find numerous references on the net to this behaviour:
>>
>>    In vim, you can just select the rectangular region with Ctrl-v,
>>    then type "I#<ESC>".  This will insert # in each line at the same
>>    column.  Very convenient.
>>
> ...
> Exuse me, but it works on my computer :) And thanks about this  
> topic, I didn't know about this feature!
>
> I selected region by Ctrl-v, pressed Shift-I and white selection  
> disappeared, I pressed # and ESC and got this effect...

Blimey! I overlooked the instruction to use the <escape> key!

Having recently made a resolution to take better advantage of vim's  
features I have only just learned selection using shift-v, so had to  
test again using ctrl-v before posting. I also tried both combinations  
using just "i" and also shift-I.

*slaps self*

Stroller.

Re: [gentoo-user] Commenting out multiple lines in vim

[Alan]

On Thu, Feb 12, 2009 at 07:53:30PM +0000, Stroller wrote:
> Hi there,
>
> I can find numerous references on the net to this behaviour:
>
>    In vim, you can just select the rectangular region with Ctrl-v,
>    then type "I#<ESC>".  This will insert # in each line at the same
>    column.  Very convenient.
>
> EG:
> http://mail.python.org/pipermail/python-list/2001-May/084540.html
> http://hurley.wordpress.com/2007/06/13/vim-tip-comment-out-multiple-lines/
>
> Yet it doesn't seem to work on any of my Gentoo systems.
>
> Is this something that is caused by a Gentoo-specific /etc/vimrc or has vim 
> evolved?

Couple of things to check:
 - you're running vim not vi or vim-tiny which has a bunch of behaviour
   removed.  Ensure that syntax highlighting works for example is what I
   do to make sure.  ESC :help will show your version also
 - ensure you're not running with the 'compatible' setting.  
        ESC :set nocompatible
   will make sure this is off

Alan
 

-- 
Alan <alan@ufies.org> - http://arcterex.net
--------------------------------------------------------------------
"Beware of computer programmers that carry screwdrivers." -- Unknown

Re: [gentoo-user] Commenting out multiple lines in vim

[Philip Webb]

090212 Stroller quoted:
>  In vim, you can just select the rectangular region with Ctrl-v,
>  then type "I#<ESC>".  This will insert # in each line at the same column.

If you want to comment a series of lines  m-n , it's quicker to do :

  :m,ns/^/#/

-- 
========================,,============================================
SUPPORT     ___________//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT    `-O----------O---'   purslowatchassdotutorontodotca

Re: [gentoo-user] Commenting out multiple lines in vim

[Stroller]

On 13 Feb 2009, at 00:53, Philip Webb wrote:

> 090212 Stroller quoted:
>> In vim, you can just select the rectangular region with Ctrl-v,
>> then type "I#<ESC>".  This will insert # in each line at the same  
>> column.
>
> If you want to comment a series of lines  m-n , it's quicker to do :
>
>  :m,ns/^/#/

I saw similar comments in my Google searches, but I am flummoxed how  
one could find it so.

Is it only on my keyboard that forward-slash is a "lower-case"  
character that is accessed *without* the shift key deployed?

How do you know m & n? Surely it's easier just to highlight the lines?

Stroller.

Re: [gentoo-user] Commenting out multiple lines in vim

[Eray Aslan]

On 13.02.2009 07:48, Stroller wrote:
> On 13 Feb 2009, at 00:53, Philip Webb wrote:
>> 090212 Stroller quoted:
>>> In vim, you can just select the rectangular region with Ctrl-v,
>>> then type "I#<ESC>".  This will insert # in each line at the same
>>> column.
>>
>> If you want to comment a series of lines  m-n , it's quicker to do :
>>
>>  :m,ns/^/#/
> 
> I saw similar comments in my Google searches, but I am flummoxed how one
> could find it so.
> 
> Is it only on my keyboard that forward-slash is a "lower-case" character
> that is accessed *without* the shift key deployed?
> 
> How do you know m & n?

Column and line numbers are shown on the lower right part of the screen.

> Surely it's easier just to highlight the lines?

Not when you are working with the keyboard most of the time.  Taking
your hands off the keyboard to use the mouse is time consuming and
becomes rather annoying.

-- 
Eray

Re: [gentoo-user] Commenting out multiple lines in vim

[Joost Roeleveld]

On Fri, February 13, 2009 7:49 am, Eray Aslan wrote:
> On 13.02.2009 07:48, Stroller wrote:
>> On 13 Feb 2009, at 00:53, Philip Webb wrote:
>>> 090212 Stroller quoted:
>>>> In vim, you can just select the rectangular region with Ctrl-v,
>>>> then type "I#<ESC>".  This will insert # in each line at the same
>>>> column.
>>>
>>> If you want to comment a series of lines  m-n , it's quicker to do :
>>>
>>>  :m,ns/^/#/
>>
>> I saw similar comments in my Google searches, but I am flummoxed how one
>> could find it so.
>>
>> Is it only on my keyboard that forward-slash is a "lower-case" character
>> that is accessed *without* the shift key deployed?
>>
>> How do you know m & n?
>
> Column and line numbers are shown on the lower right part of the screen.
>
>> Surely it's easier just to highlight the lines?
>
> Not when you are working with the keyboard most of the time.  Taking
> your hands off the keyboard to use the mouse is time consuming and
> becomes rather annoying.

True, but with this method, you don't use the mouse, just the keyboard:
1) Go to first line
2) Press <CTRL>+V
3) go to last line
4) Press <ESC>
5) Press <SHIFT>+I
6) Press '#'
7) Press <ESC>

On my system I then need to move the cursor to actually see the change, is
this normal?

--
Joost

[gentoo-user] Re: Commenting out multiple lines in vim

[Nicolas Sebrecht]

On Fri, Feb 13, 2009 at 10:24:34AM +0100, Joost Roeleveld wrote:

> True, but with this method, you don't use the mouse, just the keyboard:
> 1) Go to first line

Press gg

> 2) Press <CTRL>+V
> 3) go to last line

Press G

> 4) Press <ESC>

Why this stage ?

> 5) Press <SHIFT>+I
> 6) Press '#'
> 7) Press <ESC>
> 
> On my system I then need to move the cursor to actually see the change, is
> this normal?

I don't have to here with vim72 or gvim. However, I have no idea of how
to fix this.

-- 
Nicolas Sebrecht

Re: [gentoo-user] Re: Commenting out multiple lines in vim

[Joost Roeleveld]

On Fri, February 13, 2009 1:37 pm, Nicolas Sebrecht wrote:
>
> On Fri, Feb 13, 2009 at 10:24:34AM +0100, Joost Roeleveld wrote:
>
>> True, but with this method, you don't use the mouse, just the keyboard:
>> 1) Go to first line
>
> Press gg

Actually meant going to first line of block you want to comment out

>
>> 2) Press <CTRL>+V
>> 3) go to last line
>
> Press G

Ditto, but last line of what you want to comment out

>
>> 4) Press <ESC>
>
> Why this stage ?

Oops, typo...

>
>> 5) Press <SHIFT>+I
>> 6) Press '#'
>> 7) Press <ESC>
>>
>> On my system I then need to move the cursor to actually see the change,
>> is
>> this normal?
>
> I don't have to here with vim72 or gvim. However, I have no idea of how
> to fix this.

I use vim-7.2 as well. Could easily be because it needs that to do a
redraw of the screen.
It's a minor annoyance which I can live with. And as I am the only one
facing this, I don't see the point of raising a bug-report for it.

--
Joost

Re: [gentoo-user] Commenting out multiple lines in vim

[Stroller]

On 13 Feb 2009, at 09:24, Joost Roeleveld wrote:
> ...
> On my system I then need to move the cursor to actually see the  
> change, is
> this normal?

Here the change appears when you move the cursor... or after a slow  
second.

Stroller.

Re: [gentoo-user] Commenting out multiple lines in vim

[Joost Roeleveld]

On Fri, February 13, 2009 9:01 pm, Stroller wrote:
>
> On 13 Feb 2009, at 09:24, Joost Roeleveld wrote:
>> ...
>> On my system I then need to move the cursor to actually see the
>> change, is
>> this normal?
>
> Here the change appears when you move the cursor... or after a slow
> second.

Ok, this was clearly a case of impatience :)
Just tried it again and the change shows after about a second.

--
Joost

Re: [gentoo-user] Commenting out multiple lines in vim

[Stroller]

On 13 Feb 2009, at 06:49, Eray Aslan wrote:
> ...
>> Surely it's easier just to highlight the lines?
>
> Not when you are working with the keyboard most of the time.  Taking
> your hands off the keyboard to use the mouse is time consuming and
> becomes rather annoying.

LOL!

Stroller.

[gentoo-user] Re: Commenting out multiple lines in vim

[Nicolas Sebrecht]

On Fri, Feb 13, 2009 at 07:58:52PM +0000, Stroller wrote:

> > Not when you are working with the keyboard most of the time.  Taking
> > your hands off the keyboard to use the mouse is time consuming and
> > becomes rather annoying.
>
> LOL!

But so true.

-- 
Nicolas Sebrecht

Re: [gentoo-user] Re: Commenting out multiple lines in vim

[Stroller]

On 13 Feb 2009, at 21:45, Nicolas Sebrecht wrote:
> On Fri, Feb 13, 2009 at 07:58:52PM +0000, Stroller wrote:
>
>>> Not when you are working with the keyboard most of the time.  Taking
>>> your hands off the keyboard to use the mouse is time consuming and
>>> becomes rather annoying.
>>
>> LOL!
>
> But so true.

Sorry. I was LOLing at the idea that one might use a mouse with vim,  
or even a mouse-enabled vim.

I realised immediately after posting that this was not obvious.

Stroller.
  

Re: [gentoo-user] Commenting out multiple lines in vim

[Sebastian Dörner]

[-- Attachment #1: Type: text/plain, Size: 488 bytes --]

Hi,

Stroller wrote:
> Any comments gratefully received.
>

The ways described here are quite convenient for sure, but since
comments are pretty important and frequently-used instruments in
programming, I prefer extending the conveniency furthermore by using
"The NERD Commenter" vim plugin found here:
http://www.vim.org/scripts/script.php?script_id=1218

To comment out the 5 following lines just type 5,c<space> or 5,cs to use
multirow comments.

Regards,
Sebastian


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]