Skip to content

Instantly share code, notes, and snippets.

@orivee

orivee/gist:f55556aa80f4758812c452d858915b7d

Forked from romainl/gist:9970697
Created August 4, 2018 10:02
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save orivee/f55556aa80f4758812c452d858915b7d to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save orivee/f55556aa80f4758812c452d858915b7d to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. @romainl romainl revised this gist Jan 20, 2018. 1 changed file with 2 additions and 0 deletions.
    2 changes: 2 additions & 0 deletions gistfile1.md
    View file
    Original file line number Diff line number Diff line change
    @@ -113,6 +113,8 @@ Simply remove its directory from `~/.vim/bundle`.

    ### With Git, using submodules:

    Assuming your `.vim` directory is already a Git repository…

    $ cd ~/.vim
    $ git submodule deinit -f bundle/delimitMate
    $ git rm -rf bundle/delimitMate
  2. @romainl romainl revised this gist Jan 20, 2018. 1 changed file with 2 additions and 0 deletions.
    2 changes: 2 additions & 0 deletions gistfile1.md
    View file
    Original file line number Diff line number Diff line change
    @@ -78,6 +78,8 @@ Unzip `delimitMate-master.zip` in `~/.vim/bundle/delimitMate-master/`.

    ### With Git, using submodules:

    Assuming your `.vim` directory is already a Git repository…

    $ cd ~/.vim
    $ git submodule init
    $ git submodule add https://github.com/Raimondi/delimitMate.git bundle/delimitMate
  3. @romainl romainl revised this gist Nov 17, 2017. 1 changed file with 8 additions and 8 deletions.
    16 changes: 8 additions & 8 deletions gistfile1.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,8 +1,8 @@
    # How to use Tim Pope’s Pathogen.
    # How to use Tim Pope’s Pathogen

    I’ll assume you are on Linux or Mac OSX. For Windows, replace `~/.vim/` with `$HOME\vimfiles\` and forward slashes with backward slashes.

    ## The idea.
    ## The idea

    Vim plugins can be single scripts or collections of specialized scripts that you are supposed to put in “standard” locations under your `~/.vim/` directory. Syntax scripts go into `~/.vim/syntax/`, plugin scripts go into `~/.vim/plugin`, documentation goes into `~/.vim/doc/` and so on. That design can lead to a messy config where it quickly becomes hard to manage your plugins.

    @@ -34,20 +34,20 @@ That mechanism also applies to single-file scripts but they require a bit more w

    3. Place your script in `~/.vim/bundle/baz/syntax/baz.vim`.

    ## Prepare your environment.
    ## Prepare your environment

    If they don’t exist already, create these two directories:

    ~/.vim/autoload/
    ~/.vim/bundle/

    ## Get Pathogen.
    ## Get Pathogen

    Save `https://raw.githubusercontent.com/tpope/vim-pathogen/master/autoload/pathogen.vim` to

    ~/.vim/autoload/pathogen.vim

    ## Configure Pathogen.
    ## Configure Pathogen

    Put these lines at the top of your `vimrc`:

    @@ -58,7 +58,7 @@ Put these lines at the top of your `vimrc`:

    The two last lines have nothing to do with pathogen but, if you have them in your `~/.vimrc`, be sure to put them *after* the pathogen line. If you don’t have those lines, well… add them! What good is Vim without syntax highlighting and filetype detection?

    ## Install a plugin.
    ## Install a plugin

    We are going to install [delimitMate](https://github.com/Raimondi/delimitMate). Once it is installed in `~/.vim/bundle/`, you should get:

    @@ -88,7 +88,7 @@ Once you are back in Vim, it is recommended to execute the `:Helptags` command,

    :Helptags

    ## Update a plugin.
    ## Update a plugin

    ### Manually:

    @@ -103,7 +103,7 @@ Same as installation process.

    Use `:Helptags` to update the index of the plugin’s documentation.

    ## Remove a plugin.
    ## Remove a plugin

    ### Manually and with Git, no submodules:

  4. @romainl romainl revised this gist Jul 29, 2017. 1 changed file with 6 additions and 5 deletions.
    11 changes: 6 additions & 5 deletions gistfile1.md
    View file
    Original file line number Diff line number Diff line change
    @@ -71,12 +71,12 @@ We are going to install [delimitMate](https://github.com/Raimondi/delimitMate).

    Unzip `delimitMate-master.zip` in `~/.vim/bundle/delimitMate-master/`.

    ### Gitly, no submodules:
    ### With Git, no submodules:

    $ cd ~/.vim/bundle
    $ git clone https://github.com/Raimondi/delimitMate.git

    ### Gitly, using submodules:
    ### With Git, using submodules:

    $ cd ~/.vim
    $ git submodule init
    @@ -94,7 +94,7 @@ Once you are back in Vim, it is recommended to execute the `:Helptags` command,

    Same as installation process.

    ### Gitly, with or without submodules:
    ### With Git, with or without submodules:

    $ cd ~/.vim/bundle/delimitMate-master
    $ git pull
    @@ -105,12 +105,13 @@ Use `:Helptags` to update the index of the plugin’s documentation.

    ## Remove a plugin.

    ### Manually and gitly, no submodules:
    ### Manually and with Git, no submodules:

    Simply remove its directory from `~/.vim/bundle`.

    ### Gitly, using submodules:
    ### With Git, using submodules:

    $ cd ~/.vim
    $ git submodule deinit -f bundle/delimitMate
    $ git rm -rf bundle/delimitMate
    $ rm -rf .git/modules/bundle/delimitMate
  5. @romainl romainl revised this gist Sep 30, 2016. 1 changed file with 19 additions and 17 deletions.
    36 changes: 19 additions & 17 deletions gistfile1.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,30 +1,32 @@
    # How to use Tim Pope's Pathogen.
    # How to use Tim Pope’s Pathogen.

    I'll assume you are on Linux or Mac OSX. For Windows, replace `~/.vim/` with `$HOME\vimfiles\` and forward slashes with backward slashes.
    I’ll assume you are on Linux or Mac OSX. For Windows, replace `~/.vim/` with `$HOME\vimfiles\` and forward slashes with backward slashes.

    ## The idea.

    Vim plugins are collections of specialized scripts that you are supposed to put in "standard" locations under your `~/.vim/` directory. Syntax scripts go into `~/.vim/syntax/`, plugin scripts go into `~/.vim/plugin`, documentation goes into `~/.vim/doc/` and so on. That design can lead to a messy config where it quickly becomes hard to manage your plugins.
    Vim plugins can be single scripts or collections of specialized scripts that you are supposed to put in “standard” locations under your `~/.vim/` directory. Syntax scripts go into `~/.vim/syntax/`, plugin scripts go into `~/.vim/plugin`, documentation goes into `~/.vim/doc/` and so on. That design can lead to a messy config where it quickly becomes hard to manage your plugins.

    This is not the place to explain the technicalities behind Pathogen but the basic concept is quite straightforward: each plugin lives in its own directory under `~/.vim/bundle/`, where each directory simulates the standard structure of your `~/.vim/` directory.

    Let us take two simple, imaginary, plugins called `foo` and `bar` as an example. With the standard installation method we should have this mess:

    ~/.vim/doc/bar.txt
    ~/.vim/doc/foo.txt
    ....../plugin/bar.vim
    ............./foo.vim
    ....../syntax/bar.vim
    ~/.vim/plugin/bar.vim
    ~/.vim/plugin/foo.vim
    ~/.vim/syntax/bar.vim

    With Pathogen, we maintain the standard structure but we move it under `~/.vim/bundle/<pluginname>/`:
    With the help of Pathogen, we maintain the standard structure but we move it under `~/.vim/bundle/<pluginname>/`:

    ~/.vim/bundle/bar/plugin/bar.vim
    ................./syntax/bar.vim
    ............./foo/doc/foo.txt
    ................./plugin/foo.vim
    ~/.vim/bundle/bar/syntax/bar.vim

    ~/.vim/bundle/foo/doc/foo.txt
    ~/.vim/bundle/foo/plugin/foo.vim

    Now, our plugins are easy to delete, update or modify because they are carefully segregated from each other.

    Sometimes, you will find a single-file script that you want to install properly. In such situations, you are expected to follow this process…
    That mechanism also applies to single-file scripts but they require a bit more work.

    1. Identify the nature of that script. Is it a generic plugin? A filetype plugin? A syntax script? Let us assume it is a syntax script.

    @@ -34,7 +36,7 @@ Sometimes, you will find a single-file script that you want to install properly.

    ## Prepare your environment.

    If they don't exist already, create these two directories:
    If they don’t exist already, create these two directories:

    ~/.vim/autoload/
    ~/.vim/bundle/
    @@ -53,8 +55,8 @@ Put these lines at the top of your `vimrc`:

    filetype plugin indent on
    syntax on
    The two last lines have nothing to do with pathogen but, if you have them in your `~/.vimrc`, be sure to put them *after* the pathogen line. If you don't have those lines, well… add them! What good is Vim without syntax highlighting and filetype detection?

    The two last lines have nothing to do with pathogen but, if you have them in your `~/.vimrc`, be sure to put them *after* the pathogen line. If you don’t have those lines, well… add them! What good is Vim without syntax highlighting and filetype detection?

    ## Install a plugin.

    @@ -82,7 +84,7 @@ Unzip `delimitMate-master.zip` in `~/.vim/bundle/delimitMate-master/`.

    ### All methods:

    Once you are back in Vim, it is recommended to execute the `:Helptags` command, provided by Pathogen, to make the plugin's documentation available globally:
    Once you are back in Vim, it is recommended to execute the `:Helptags` command, provided by Pathogen, to make the plugin’s documentation available globally:

    :Helptags

    @@ -99,7 +101,7 @@ Same as installation process.

    ### Both methods:

    Use `:Helptags` to update the index of the plugin's documentation.
    Use `:Helptags` to update the index of the plugin’s documentation.

    ## Remove a plugin.

    @@ -111,4 +113,4 @@ Simply remove its directory from `~/.vim/bundle`.

    $ cd ~/.vim
    $ git submodule deinit -f bundle/delimitMate
    $ git rm -rf bundle/delimitMate
    $ git rm -rf bundle/delimitMate
  6. @romainl romainl revised this gist Jul 8, 2015. 1 changed file with 3 additions and 1 deletion.
    4 changes: 3 additions & 1 deletion gistfile1.md
    View file
    Original file line number Diff line number Diff line change
    @@ -82,7 +82,9 @@ Unzip `delimitMate-master.zip` in `~/.vim/bundle/delimitMate-master/`.

    ### All methods:

    It is recommended to use the `:Helptags` command, provided by Pathogen, to make the plugin's documentation available.
    Once you are back in Vim, it is recommended to execute the `:Helptags` command, provided by Pathogen, to make the plugin's documentation available globally:

    :Helptags

    ## Update a plugin.

  7. @romainl romainl revised this gist Jan 30, 2015. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion gistfile1.md
    View file
    Original file line number Diff line number Diff line change
    @@ -4,7 +4,7 @@ I'll assume you are on Linux or Mac OSX. For Windows, replace `~/.vim/` with `$H

    ## The idea.

    Vim plugins are collections of specialized scripts that you are supposed to put in "standard" locations under your `~/.vim/` directory. Syntax scripts go into `~/.vim/syntax/`, plugin scripts go into `~/.vim/plugin`, documentation goes into `~/.vim/doc/` and so on. That design can lead to a messy config where it can become hard to manage your plugins.
    Vim plugins are collections of specialized scripts that you are supposed to put in "standard" locations under your `~/.vim/` directory. Syntax scripts go into `~/.vim/syntax/`, plugin scripts go into `~/.vim/plugin`, documentation goes into `~/.vim/doc/` and so on. That design can lead to a messy config where it quickly becomes hard to manage your plugins.

    This is not the place to explain the technicalities behind Pathogen but the basic concept is quite straightforward: each plugin lives in its own directory under `~/.vim/bundle/`, where each directory simulates the standard structure of your `~/.vim/` directory.

  8. @romainl romainl revised this gist Jan 30, 2015. 1 changed file with 30 additions and 0 deletions.
    30 changes: 30 additions & 0 deletions gistfile1.md
    View file
    Original file line number Diff line number Diff line change
    @@ -2,6 +2,36 @@

    I'll assume you are on Linux or Mac OSX. For Windows, replace `~/.vim/` with `$HOME\vimfiles\` and forward slashes with backward slashes.

    ## The idea.

    Vim plugins are collections of specialized scripts that you are supposed to put in "standard" locations under your `~/.vim/` directory. Syntax scripts go into `~/.vim/syntax/`, plugin scripts go into `~/.vim/plugin`, documentation goes into `~/.vim/doc/` and so on. That design can lead to a messy config where it can become hard to manage your plugins.

    This is not the place to explain the technicalities behind Pathogen but the basic concept is quite straightforward: each plugin lives in its own directory under `~/.vim/bundle/`, where each directory simulates the standard structure of your `~/.vim/` directory.

    Let us take two simple, imaginary, plugins called `foo` and `bar` as an example. With the standard installation method we should have this mess:

    ~/.vim/doc/foo.txt
    ....../plugin/bar.vim
    ............./foo.vim
    ....../syntax/bar.vim

    With Pathogen, we maintain the standard structure but we move it under `~/.vim/bundle/<pluginname>/`:

    ~/.vim/bundle/bar/plugin/bar.vim
    ................./syntax/bar.vim
    ............./foo/doc/foo.txt
    ................./plugin/foo.vim

    Now, our plugins are easy to delete, update or modify because they are carefully segregated from each other.

    Sometimes, you will find a single-file script that you want to install properly. In such situations, you are expected to follow this process…

    1. Identify the nature of that script. Is it a generic plugin? A filetype plugin? A syntax script? Let us assume it is a syntax script.

    2. Come up with a descriptive name for that single-file plugin, say `baz`.

    3. Place your script in `~/.vim/bundle/baz/syntax/baz.vim`.

    ## Prepare your environment.

    If they don't exist already, create these two directories:
  9. @romainl romainl revised this gist Jan 20, 2015. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion gistfile1.md
    View file
    Original file line number Diff line number Diff line change
    @@ -48,7 +48,7 @@ Unzip `delimitMate-master.zip` in `~/.vim/bundle/delimitMate-master/`.

    $ cd ~/.vim
    $ git submodule init
    $ git submodule add htps://github.com/Raimondi/delimitMate.git bundle/delimitMate
    $ git submodule add https://github.com/Raimondi/delimitMate.git bundle/delimitMate

    ### All methods:

  10. @romainl romainl revised this gist Aug 13, 2014. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion gistfile1.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,6 +1,6 @@
    # How to use Tim Pope's Pathogen.

    I'll assume you are on Linux or Mac OSX. For Windows, replace `~/.vim/` with `$HOME/vimfiles/`.
    I'll assume you are on Linux or Mac OSX. For Windows, replace `~/.vim/` with `$HOME\vimfiles\` and forward slashes with backward slashes.

    ## Prepare your environment.

  11. @romainl romainl revised this gist Jul 11, 2014. 1 changed file with 9 additions and 2 deletions.
    11 changes: 9 additions & 2 deletions gistfile1.md
    View file
    Original file line number Diff line number Diff line change
    @@ -20,12 +20,11 @@ Save `https://raw.githubusercontent.com/tpope/vim-pathogen/master/autoload/patho
    Put these lines at the top of your `vimrc`:

    execute pathogen#infect()
    execute pathogen#helptags()

    filetype plugin indent on
    syntax on

    The two last lines have nothing to do with pathogen but, if you have them in your `~/.vimrc`, be sure to put them *after* the pathogen lines. If you don't have those lines, well… add them! What good is Vim without syntax highlighting and filetype detection?
    The two last lines have nothing to do with pathogen but, if you have them in your `~/.vimrc`, be sure to put them *after* the pathogen line. If you don't have those lines, well… add them! What good is Vim without syntax highlighting and filetype detection?

    ## Install a plugin.

    @@ -51,6 +50,10 @@ Unzip `delimitMate-master.zip` in `~/.vim/bundle/delimitMate-master/`.
    $ git submodule init
    $ git submodule add htps://github.com/Raimondi/delimitMate.git bundle/delimitMate

    ### All methods:

    It is recommended to use the `:Helptags` command, provided by Pathogen, to make the plugin's documentation available.

    ## Update a plugin.

    ### Manually:
    @@ -62,6 +65,10 @@ Same as installation process.
    $ cd ~/.vim/bundle/delimitMate-master
    $ git pull

    ### Both methods:

    Use `:Helptags` to update the index of the plugin's documentation.

    ## Remove a plugin.

    ### Manually and gitly, no submodules:
  12. @romainl romainl revised this gist Jun 24, 2014. 1 changed file with 23 additions and 7 deletions.
    30 changes: 23 additions & 7 deletions gistfile1.md
    View file
    Original file line number Diff line number Diff line change
    @@ -29,31 +29,47 @@ The two last lines have nothing to do with pathogen but, if you have them in you

    ## Install a plugin.

    ### Manually:

    Unzip `delimitMate-master.zip` in `~/.vim/bundle/`, you should get:
    We are going to install [delimitMate](https://github.com/Raimondi/delimitMate). Once it is installed in `~/.vim/bundle/`, you should get:

    ~/.vim/bundle/delimitMate-master/autoload/...
    ~/.vim/bundle/delimitMate-master/doc/...
    ~/.vim/bundle/delimitMate-master/plugin/...
    ~/.vim/bundle/delimitMate-master/...

    ### Gitly:
    ### Manually:

    Unzip `delimitMate-master.zip` in `~/.vim/bundle/delimitMate-master/`.

    ### Gitly, no submodules:

    $ cd ~/.vim/bundle
    $ git clone https://github.com/Raimondi/delimitMate.git

    ### Gitly, using submodules:

    $ cd ~/.vim
    $ git submodule init
    $ git submodule add htps://github.com/Raimondi/delimitMate.git bundle/delimitMate

    ## Update a plugin.

    ### Manually:

    Same as installation process.

    ### Gitly:
    ### Gitly, with or without submodules:

    $ cd ~/.vim/bundle/delimitMate
    $ cd ~/.vim/bundle/delimitMate-master
    $ git pull

    ## Remove a plugin.

    Simply remove its directory from `~/.vim/bundle`.
    ### Manually and gitly, no submodules:

    Simply remove its directory from `~/.vim/bundle`.

    ### Gitly, using submodules:

    $ cd ~/.vim
    $ git submodule deinit -f bundle/delimitMate
    $ git rm -rf bundle/delimitMate
  13. @romainl romainl revised this gist Apr 28, 2014. 1 changed file with 4 additions and 1 deletion.
    5 changes: 4 additions & 1 deletion gistfile1.md
    View file
    Original file line number Diff line number Diff line change
    @@ -21,8 +21,11 @@ Put these lines at the top of your `vimrc`:

    execute pathogen#infect()
    execute pathogen#helptags()
    syntax on

    filetype plugin indent on
    syntax on

    The two last lines have nothing to do with pathogen but, if you have them in your `~/.vimrc`, be sure to put them *after* the pathogen lines. If you don't have those lines, well… add them! What good is Vim without syntax highlighting and filetype detection?

    ## Install a plugin.

  14. @romainl romainl revised this gist Apr 4, 2014. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion gistfile1.md
    View file
    Original file line number Diff line number Diff line change
    @@ -38,7 +38,7 @@ Unzip `delimitMate-master.zip` in `~/.vim/bundle/`, you should get:
    ### Gitly:

    $ cd ~/.vim/bundle
    $ git clone git@github.com:Raimondi/delimitMate.git
    $ git clone https://github.com/Raimondi/delimitMate.git

    ## Update a plugin.

  15. @romainl romainl revised this gist Apr 4, 2014. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion gistfile1.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,4 +1,4 @@
    # INSTALLING PATHOGEN
    # How to use Tim Pope's Pathogen.

    I'll assume you are on Linux or Mac OSX. For Windows, replace `~/.vim/` with `$HOME/vimfiles/`.

  16. @romainl romainl created this gist Apr 4, 2014.
    56 changes: 56 additions & 0 deletions gistfile1.md
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,56 @@
    # INSTALLING PATHOGEN

    I'll assume you are on Linux or Mac OSX. For Windows, replace `~/.vim/` with `$HOME/vimfiles/`.

    ## Prepare your environment.

    If they don't exist already, create these two directories:

    ~/.vim/autoload/
    ~/.vim/bundle/

    ## Get Pathogen.

    Save `https://raw.githubusercontent.com/tpope/vim-pathogen/master/autoload/pathogen.vim` to

    ~/.vim/autoload/pathogen.vim

    ## Configure Pathogen.

    Put these lines at the top of your `vimrc`:

    execute pathogen#infect()
    execute pathogen#helptags()
    syntax on
    filetype plugin indent on

    ## Install a plugin.

    ### Manually:

    Unzip `delimitMate-master.zip` in `~/.vim/bundle/`, you should get:

    ~/.vim/bundle/delimitMate-master/autoload/...
    ~/.vim/bundle/delimitMate-master/doc/...
    ~/.vim/bundle/delimitMate-master/plugin/...
    ~/.vim/bundle/delimitMate-master/...

    ### Gitly:

    $ cd ~/.vim/bundle
    $ git clone git@github.com:Raimondi/delimitMate.git

    ## Update a plugin.

    ### Manually:

    Same as installation process.

    ### Gitly:

    $ cd ~/.vim/bundle/delimitMate
    $ git pull

    ## Remove a plugin.

    Simply remove its directory from `~/.vim/bundle`.