To begin diffing on all visible windows:

    :windo diffthis
which executes `:diffthis` on each window.

To end diff mode:

    :diffoff!
(The `!` makes `diffoff` apply to all windows of the current tab - it&#39;d be nice if `diffthis` had the same feature, but it doesn&#39;t.)

in each of the windows you want to diff type:

    :diffthis

If you want to diff all of the open windows, you can do:
  
    :windo diffthis

(`windo` will apply the command to all open windows)

Following up on the earlier answers, 

 * `:windo difft` (short for `diffthis`) will start diff mode in all the open windows.
 * `:windo diffo` (short for `diffoff`) will stop diff mode in all the open windows.

I have the following mappings in my `vimrc` to make it easier:

    command! Difft windo diffthis
    command! Diffo windo diffoff


Following on the earlier answers I adapted the mapping provided by @cxw. The following mapping automatically closes **NERDTree** and diffs the open windows. It does not matter if **NERDTree** is closed, it works the same way. I do this quite often so it saved me quite some time.

    command! Difft NERDTreeClose | windo diffthis




When I use a specialized template in different object files, I get a &quot;multiple definition&quot; error when linking. The only solution I found involves using the &quot;inline&quot; function, but it just seems like some workaround. How do I solve that without using the &quot;inline&quot; keyword? If that&#39;s not possible, why?

Here is the example code:

    paulo@aeris:~/teste/cpp/redef$ cat hello.h 
    #ifndef TEMPLATE_H
    #define TEMPLATE_H
    
    #include &lt;iostream&gt;
    
    template &lt;class T&gt;
    class Hello
    {
    public:
        void print_hello(T var);
    };
    
    template &lt;class T&gt;
    void Hello&lt;T&gt;::print_hello(T var)
    {
        std::cout &lt;&lt; &quot;Hello generic function &quot; &lt;&lt; var &lt;&lt; &quot;\n&quot;;
    }

    template &lt;&gt; //inline
    void Hello&lt;int&gt;::print_hello(int var)
    {
        std::cout &lt;&lt; &quot;Hello specialized function &quot; &lt;&lt; var &lt;&lt; &quot;\n&quot;;
    }

    #endif

---

    paulo@aeris:~/teste/cpp/redef$ cat other.h 
    #include &lt;iostream&gt;
    
    void other_func();

---

    paulo@aeris:~/teste/cpp/redef$ cat other.c 
    #include &quot;other.h&quot;
    
    #include &quot;hello.h&quot;
    
    void other_func()
    {
        Hello&lt;char&gt; hc;
        Hello&lt;int&gt; hi;
    
        hc.print_hello(&#39;a&#39;);
        hi.print_hello(1);
    }

---


    paulo@aeris:~/teste/cpp/redef$ cat main.c 
    #include &quot;hello.h&quot;
    
    #include &quot;other.h&quot;
    
    int main()
    {
        Hello&lt;char&gt; hc;
        Hello&lt;int&gt; hi;
    
        hc.print_hello(&#39;a&#39;);
        hi.print_hello(1);
    
        other_func();
    
        return 0;
    }

---

    paulo@aeris:~/teste/cpp/redef$ cat Makefile
    all:
        g++ -c other.c -o other.o -Wall -Wextra
        g++ main.c other.o -o main -Wall -Wextra

---

Finally:


    paulo@aeris:~/teste/cpp/redef$ make
    g++ -c other.c -o other.o -Wall -Wextra
    g++ main.c other.o -o main -Wall -Wextra
    other.o: In function `Hello&lt;int&gt;::print_hello(int)&#39;:
    other.c:(.text+0x0): multiple definition of `Hello&lt;int&gt;::print_hello(int)&#39;
    /tmp/cc0dZS9l.o:main.c:(.text+0x0): first defined here
    collect2: ld returned 1 exit status
    make: ** [all] Erro 1


If I uncomment the &quot;inline&quot; inside hello.h, the code will compile and run, but that just seems like some kind of &quot;workaround&quot; to me: what if the specialized function is big and used many times? Will I get a big binary? Is there any other way to do this? If yes, how? If not, why?

I tried to look for answers, but all I got was &quot;use inline&quot; without any further explanation.

Thanks

multiple definition of template specialization when using different objects

If I have an object like: 

    { &#39;a&#39; : &#39;apple&#39;, &#39;b&#39; : &#39;banana&#39;, &#39;c&#39; : &#39;carrot&#39; }

If I don&#39;t know in advance that the list goes up to &#39;c&#39;, other than looping through the object, is there a way to get the last item in the object (e.g. `&#39;carrot&#39;`)?

getting the last item in a javascript object

I&#39;ve have two files opened. They are opened in vertical mode, next to next. Can I instantly diff these two files without leaving or closing Vim ?

Take diff of two vertical opened windows in Vim

<p>I've have two files opened. They are opened in vertical mode, next to next. Can I instantly diff these two files without leaving or closing Vim ?</p>


What is the correct name of the Vim scripting language? I see it being called **VimScript**, **Vim script** and even **VimL**.

VimL is even listed on GitHub as the [10th most popular programming language][1]! What is the history behind the VimL name? Why are the Git folks calling it VimL?


  [1]: https://github.com/languages/VimL

VimScript or VimL?

When a buffer gets deleted (via the `:bd[elete]` command), it not only deletes the buffer but also removes the split window that buffer was in.

Is there a way to delete/unload a buffer and keep the window split?

How to delete a buffer in Vim without losing the split window?

How to move cursor to the n-th symbol from the left in Vim?

One of the solutions I see is press `0n&lt;right-arrow&gt;`, it will move to the n+1 position. Is there any more natural way to do it?

Go to n-th symbol in line

In my Vimscript program, I need to open an additional Vim buffer that is not immediately associated with a file, but which the user can save to a file of her/his choosing, just like the initial buffer called `[No Name]`. How can I do this?

Vim: How do you open another [No Name] buffer like the one on startup?

I use the shortcut &lt;kbd&gt;w&lt;/kbd&gt; to move the cursor one word right. Is there a shortcut to move a word left?


How to move one word left in the vi editor

In .git/config I tried:

    [diff]
        patience = true

But no luck

Do I have to do:
 
    git diff --patience
    git show --patience HEAD
etc., every time?

How to set patience as default git diff algorithm

For the problem I&#39;m working on, finding distances between two sequences to determine their similarity, sequence order is very important. However, the sequences that I have are not all the same length, so I pad any deficient strings with empty points such that both sequences are the same length in order to satisfy the Hamming distance requirement. Is there any major problem with me doing this, since all I care about are the number of transpositions (not insertions or deletions like Levenshtein does)?

I&#39;ve found that Hamming distance is much, much faster than Levenshtein as a distance metric for sequences of longer length. When should one use Levenshtein distance (or derivatives of Levenshtein distance) instead of the much cheaper Hamming distance? Hamming distance can be considered the upper bound for possible Levenshtein distances between two sequences, so if I am comparing the two sequences for a order-biased similarity metric rather than the absolute minimal number of moves to match the sequences, there isn&#39;t an apparent reason for me to choose Levenshtein over Hamming as a metric, is there?



Hamming Distance vs. Levenshtein Distance

I don&#39;t see a difference between the output of &#39;git format-patch&#39; and &#39;git diff&#39;, is there any? And won&#39;t I be able to use &#39;git diff&#39; to produce a patch and then apply it using git apply?

My problem is that I have changes added to the index, but apparently git format-patch only accepts commits, so if I can use the output of diff, then I can use this command to produce a patch for the changes in the index:

    git diff --cached &gt; index.patch


What is the difference between &#39;git format-patch and &#39;git diff&#39;?

I like the output formatting of `git diff`.  The color and the `+`/`-` representation of changes between lines is easier to read than GNU diff.

I can run `git diff` using `--no-index` flag outside of a git repo and it works fine. However, it appears to be missing the `--exclude` option for excluding files or subdirectories from a recursive `diff`. 

Is there a way to get the best of both worlds? (color options and `+`/`-` format of `git diff` and `--exclude` option of GNU diff).  

I&#39;ve experimented with [`colordiff`](http://colordiff.sourceforge.net/), but I still prefer the output format of `git diff`

How to get diff working like git-diff?

I want to check the real diff between remote branch and local branch. How can I do that?

Issuing the below command partially works, but it shows the diff of the new changes of my local branch too.

    git diff remote/branch


How to check real git diff before merging from remote branch?

I&#39;ve started using vimdiff today, and wanted to do some of the things that I&#39;ve taken for granted on Windows based diff editors (like expand/collapse a diff section, have full file expansion/only diffs with three context lines above or below, etc.). I currently know only the following commands:

Keyboard Shortcuts:

- &lt;kbd&gt;d&lt;/kbd&gt;&lt;kbd&gt;o&lt;/kbd&gt; - Get changes from other window into the current window.

- &lt;kbd&gt;d&lt;/kbd&gt;&lt;kbd&gt;p&lt;/kbd&gt; - Put the changes from current window into the other window.

- &lt;kbd&gt;]&lt;/kbd&gt;&lt;kbd&gt;c&lt;/kbd&gt; - Jump to the next change.

- &lt;kbd&gt;[&lt;/kbd&gt;&lt;kbd&gt;c&lt;/kbd&gt; - Jump to the previous change.

- &lt;kbd&gt;Ctrl&lt;/kbd&gt;+&lt;kbd&gt;W&lt;/kbd&gt;, &lt;kbd&gt;w&lt;/kbd&gt; - Switch to the other split window (&lt;kbd&gt;Ctrl&lt;/kbd&gt; + &lt;kbd&gt;W&lt;/kbd&gt;, &lt;kbd&gt;Ctrl&lt;/kbd&gt; + &lt;kbd&gt;W&lt;/kbd&gt; does the same thing, in case you let go of the &lt;kbd&gt;Ctrl&lt;/kbd&gt; key a bit later)

Could someone point me to the right direction so I could replicate similar features?

It would be nice if I could expand/collapse lines around the diffs, for example.




How can I expand/collapse a diff sections in Vimdiff?

[I already know](http://vimdoc.sourceforge.net/htmldoc/options.html#%27diffopt%27) how to use the `diffopt` variable to start diff mode with horizontal/vertical splits but not how to toggle between the two when I already have two files open for comparison.

I tried the accepted answer found in [this older post](https://stackoverflow.com/questions/1269603/to-switch-from-vertical-split-to-horizontal-split-fast-in-vim), but to no avail. The Ctrl+W commands didn&#39;t work for me. Perhaps because I&#39;m running gVim in Windows-friendly mode?


How do I toggle between a Vertical and a Horizontal split in vimdiff?

vim-fugitive side-by-side git diff is great for viewing diff of unstaged files.

How can I use vim-fugitive to git diff

 - staged files? 
 - any git revision?

How can I view git diff for any commit using vim-fugitive?

How do you quit all windows with a single command in Vim or `vimdiff`?

`:q` only quits out of the active window, so then a separate `:q` is needed to close each window.

  [1]: https://stackoverflow.com/search?q=vim%20quit%20all%20windows


Content Type	Original Author	Original Content on Stackoverflow
Question	Fatih Arslan	View Question on Stackoverflow
Solution 1 - Vim	Nefrubyr	View Answer on Stackoverflow
Solution 2 - Vim	Nathan Fellman	View Answer on Stackoverflow
Solution 3 - Vim	cxw	View Answer on Stackoverflow
Solution 4 - Vim	Jordi Freixa	View Answer on Stackoverflow

Take diff of two vertical opened windows in Vim

Vim Problem Overview

Vim Solutions

Solution 1 - Vim

Solution 2 - Vim

Solution 3 - Vim

Solution 4 - Vim

getting the last item in a javascript object

multiple definition of template specialization when using different objects

Attributions