Carriage return vs newline in vim

newlinesvim

In vim, when I opened a file, I wanted to add two empty lines at the end of each current line. I used the following switch:

%s/$/\n\n/

Apparently, this does not work, but what does work is:

%s/$/\r\r/

I thought \r is a Windows feature? Would anyone be able to explain a bit more.

Best Answer

From vim docs on patterns:

\r matches <CR>

\n matches an end-of-line - When matching in a string instead of buffer text a literal newline character is matched.

Source: https://stackoverflow.com/questions/71417/why-is-r-a-newline-for-vim

Related Solutions

Vi vs Vim – Reasons to Use Vi Over Vim

vi is (also) a POSIX standard editor. There are plenty of implementations and vim is likely the most popular.

While many traditional Unix compliant OSes provide vi implementations very close to the standard, vim has added a lot of extra features that make it a double-edged sword.

Of course, these extensions are usually designed to ease the editing process and provide useful features and functionalities. However, once you are used to some of them (not the cosmetic ones like syntax coloring but those that change the editor's behavior) you can easily forget they are specific; and using a different implementation, including the ones based on the original BSD code can be very frustrating. The opposite is also true.

This is quite similar to the issue that happens with scripts using non POSIX bashisms faced to more orthodox shell implementations like dash or ksh.

Why does Vim only activate the highlight configuration after I source the .vimrc manually

The issue is caused by the sensible plugin:line 93. :help t_Co

" Allow color schemes to do bright colors without forcing bold.
if &t_Co == 8 && $TERM !~# '^linux'
  set t_Co=16  " << --- Causes hickup
endif

If you run vim in verbose log mode (vim -V15load_log.vim) – and search for t_Co= and RedundantSpaces you'll see that sensible is actually parsed after your appearance.vim file.

Quick fix would be to either comment out that section of the code and add it to your .vimrc, but as you link to git repositories that is perhaps not what you want.

A different approach would be to move it out of the bundledirectory and add it as a separate source line in your vimrc, before your glob loop.

I.e.:

  source ~/.vim/hacks/vim-sensible/plugin/sensible.vim

  for f in split(glob ...

Another way would be to load custom highlight on BufLoad.

Etc. …

Best Answer

Related Solutions

Vi vs Vim – Reasons to Use Vi Over Vim

Why does Vim only activate the highlight configuration after I source the .vimrc manually

Related Question