Difference between revisions of "Vim Tips & Tricks"

From LinuxMCE
Jump to: navigation, search
(Writing code)
Line 1: Line 1:
<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007.  In general any information should apply to LinuxMCE.  However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table>Source: [http://jmcpherson.org/editing.html Efficient Editing With vim]
+
</table>Source: [http://jmcpherson.org/editing.html Efficient Editing With vim]
  
 
==Writing code==
 
==Writing code==
Line 12: Line 12:
 
[[Category: Internal Documents]]
 
[[Category: Internal Documents]]
 
[[Category: Tutorials]]
 
[[Category: Tutorials]]
 +
[[Category: Programmer's Guide]]

Revision as of 15:02, 24 August 2007

</table>Source: Efficient Editing With vim

Writing code

Ctrl+n or Ctrl+p 
Autocomplete ;)
]p 
Just like p, but it automatically adjusts the indent level of the pasted code to match that of the code you paste into. Try it!
Putting the cursor on a brace, bracket, or parenthese and pressing % will send the cursor to the matching brace, bracket, or parenthese. Great for fixing parse problems related to heavily nested blocks of code or logic.
>> 
Indent the highlighted code. (See the earlier section about efficient text selection. If no text is selected, the current line is indented.)
<< 
Like >>, but un-indents.
gd 
Go to the definition (or declaration) of the function or variable under the cursor.
Go to the man page for the word currently under the cursor. (For instance, if your cursor is currently over the word sleep, you will see the man page for sleep displayed.)