VIM
Get flash to fully experience Pearltrees
Vim_Plugins
Tagbar is a vim plugin for browsing the tags of source code files. It provides a sidebar that displays the ctags-generated tags of the current file, ordered by their scope. This means that for example methods in C++ are displayed under the class they are defined in. Extract the archive or clone the repository into a directory in your 'runtimepath' or use pathogen . Don't forget to run :helptags if you don't use pathogen. Note: Vim versions
Tagbar, the Vim class outline viewer
Tagbar - Display tags of the current file ordered by scope : vim online
Tagbar displays the tags of the current file in a sidebar, similar to vimscript #273 . But it has the advantage that it will display them ordered by their scope -- for example, methods and members in languages like C++, Python or Java will be listed under their correct class instead of just under the general categories 'functions' or 'variables'. This gives a more helpful overview of the file. If ctags is not installed in one of the directories in your $PATH environment variable you have to set the option g:tagbar_ctags_bin, see the documentation for exact instructions.
You're working on a project where you need to jump between occurrences of significant keywords, which are possibly spread across multiple files. For example, you're writing source code and want to be able to type a function name then quickly jump to where it was initially defined so you understand how it should be used. Then you want to return to where you were. We will use a program called Exuberant Ctags to generate the tag list because it is compatible with popular programming languages such as C, C++, Java, Lisp, Perl, PHP, Python, and Ruby. After you have installed Ctags you can generate a tag list for the current directory (and its sub-directories) with ctags -R . To only consider files in the current directory use ctags * .
Vim Recipes: Navigating Tags
Continuing with upgrading and explaining my Vim setup , I'm going to cover Tagbar and TagList today. Both are plugins that provide high-level views of your source code at a class and function level, similar to Eclipse, Visual Studio, or other IDEs. The view is available in a quick toggle sidebar, which you can sort and use to jump around in your source file. Both plugins make use of Ctags , which parses the source code for most popular languages. Having a high level view is great for understanding new code, getting a quick layout of a file, and simplifying your interaction with a source file; working with classes and functions, not line numbers and searching.
/code - a blog
Genau wie es für ZSH und BASH die .zshrc und die .bashrc gibt, existiert auch eine .vimrc für Vim. Man findet sie im Home-Verzeichnis des jeweiligen Users. Die .vimrc wird von Vim bei jedem Start ausgelesen.
Vim konfigurieren per .vimrc « Ubuntu Linux Blog
Vim made easy: how to get your favorite IDE features in Vim
The Vim text editor is a favorite of many programmers and system administrators. Although it provides an exceptional amount of power and flexibility, it can be somewhat intimidating for new users. Programmers who transition to Vim from a conventional integrated development environment (IDE) tend to find the paradigm shift a bit disorienting. I often get e-mail from readers who are looking for ways to make Vim more developer-friendly. A common complaint is that the editor doesn't come with standard IDE features out of the box and it's not always clear how to configure it to provide equivalent functionality.
Emacs for vi users
This is intended as an introductory guide for vi users wishing to learn the basics of Emacs. I'm writing it because I'm one of them, and I suspect that I'm not alone in being mystified by the lack of a command mode, text objects and an underlying ex editor, as well as the plethora of strange and unfamiliar key combinations. The intent is to give fledgling Emacs users a basic set of commands, sufficient for basic editing. This page is a basic Emacs survival guide for the vi user. It is grounded in familiarity of vi and (quite naturally) assumes a vi-centric view of the world.
module foo contains subroutine hello() end subroutine hello subroutine hello() end subroutine subroutine hello() end subroutine end module foo subroutine hello() end subroutine subroutine hello() end subroutine subroutine hello() end subroutine The annoying thing is the following. If I cut (dd) and paste (P) a folded subroutine outside the module/end module block, the freshly pasted fold stay closed.
vim opens my folds on paste. how to prevent that ? - Programmers Solution - JustLogged
taken from here : If you ever edited text and still wanted to make your lines break at about 70 characters, you know it's sometimes needed to "rewrap" the lines to make them fill those 70 characters again. VIM has the ideal solution for this. Select a block of text and press gq . Instant rewrap!
rewrapping paragraphs in vim
That will automatically wrap text as close to 79 characters as white space allows without exceeding the 79 character limit. This option wraps at word boundaries. If you want to apply this to specific areas; bring the cursor at the beginning of the text you want to format and type gq . Now specify the range, say $ to format a large line. :set wm=2
Automatic word wrapping - Vim Tips Wiki
Do you program in vim? Have you heard of exuberant ctags? No, then download it to your machine immediately, if ctags is not already in your system http://ctags.sourceforge.net/ Trust me - this simple program can save hours of frustration.
Search results for exuberant ctags
On Fri, Aug 31, 2001 at 12:49:53AM -0400, Steve Dondley wrote: | I've heard of problems with emacs and the backspace and delete key not | working properly. Now I'm wondering what the correct behavior for vi is. | My keys seem to be acting a funny. The biggest problem with backspace vs. delete was caused by some terminal manufacturer many years ago. The button on your keyboard in the upper right corner that usually has the glyphs "backspace" on it originally sent ASCII character 127 to the host. This was with vt100's or something "original" like that.
Re: vi: backspace and delete key
by Steve Oualline This is the Vim cookbook page. It contains short recipes for doing many simple and not so simple things in Vim . You should already know the basics of Vim , however each command is explained in detail.
Vim Cookbook
1. Installation Conque is designed for both Unix and Windows operating systems, however the requirements are slightly different. Please check section below corresponding to your installed OS.
Usage - conque - Run interactive commands inside a Vim buffer - Google Project Hosting
If you were using Janus before January 2012, note that Janus has gone through a rewrite to make it more stable and customizable. Most notably, you can now disable plugins using janus#disable_plugin and customize Janus using ~/.vimrc.before and ~/.vimrc.after . See the rest of this README and the Customization wiki page . NOTE: If you ever have an error updating Janus relating to a missing commit in a submodule, please try running rake again before submitting an issue.