I will highlight some of the more advanced uses of maps:
Historians write a lot of text. A helpful and supportive editor is crucial for their day to day work. In this talk I will introduce some of neo/vim's features and plugins I find most useful while dealing with text. Apart from several vim commands and settings, I will go into detail especially with regard to editing LaTeX and markdown files as well as using git.
This talk will provide initial guidelines on writing vim helpfiles. User documentation is one of the important aspects of any software. Because vim has a great functionality of dealing helpfile inside the editor, it is very important to write helpfile accessible inside vim editor and not anywhere else. Ideally, the talk will cover below points.
Recently I was trying to observe various vim plugins helpful for writers. Some commonly suggested goyo. I was shocked to find that this plugin was not contained any vim specific helpfile. I request the author to take the responsibility of writing vim specific helpfile for this plugin, but he didn't agree with that decision at that time reference. I decided to write the helpfile for goyo plugin and wrote goyo-doc. By doing this task I learned the syntax of vim helpfile. I think it is good to discuss the importance of vim specific helpfile with a community and guide them on writing them.
Everybody knows that VIM is the best and fastest text editor, but some PHP developers change it for other IDEs like PHPStorm, Netbeans... In this talk we will explain that you can to have the best editor and all necessary features that we must find in a complete IDE at the same time:
We are happy to announce Büro 2.0 as the host for Vimfest 2017.
Here is the exact location of the place:
Büro 2.0 Weigandufer 45, 12059 Berlin
VIM currently lacks many of the introspection and completion features (Intellisense) for PHP that are taken from granted in IDEs such as PHPStorm. Despite this handicap many PHP developers still opt to use VIM because of its speed and power.
The reason for this lack would perhaps be the amount of time and effort required to implement these features, many projects have been started, none (of which I am aware) have succeeded in becoming stable solutions.
In this talk Dan will discuss his view of the quest for PHP intellisense in VIM and a new PHP refactoring tool (and VIM plugin) which he has been working on.
I would like to highlight the abilities that I have assembled, to make Vim a good IDE for any language. These abilities involve easy file searching, grepping, syntax highlighting, and formatting of code to start. Sometimes there is a builtin way to accomplish something, sometimes through finding the right plugin, and sometimes through hacking up some Vimscript. Often, there are multiple ways of accomplishing something and you are free to make the choice. I'd like to share the choices I've made and hopefully improve your experience in VIM.
If you plan to visit our event this year, please signup on doodle.
Please mark on which days you want to be at the event, what kind of food you eat (carni, veget, vegan), and if you need help finding with an accommodation.
Let us know if you want to attend so that we can plan the location and program around Vimfest.
The group of Vimfest visitors in 2016. You can find more images on flickr.
:earlierit's used to go back in the history (check out https://github.com/mbbill/undotree (preferred) and http://sjl.bitbucket.org/gundo.vim/ to visualize the tree)
@:repeat the last command (=> therefore space can be kept as a leader, especially since after @: you can just use
@@to rerun the command)
<C-y>repeat the words above the cursor
<C-Alt>will trigger block select for the mouse (not a Vim feature; depends on your terminal emulator) => works for xfce-terminal and ROXterm
:redir, that can use the new execute() function (e.g.
The following talks have been recorded