<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Want to try living in vim</title>
	<atom:link href="http://changelog.complete.org/archives/589-want-to-try-living-in-vim/feed" rel="self" type="application/rss+xml" />
	<link>http://changelog.complete.org/archives/589-want-to-try-living-in-vim</link>
	<description>Viewpoints on technology, society, and government</description>
	<lastBuildDate>Sun, 05 Feb 2012 03:11:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Karl</title>
		<link>http://changelog.complete.org/archives/589-want-to-try-living-in-vim/comment-page-1#comment-1741</link>
		<dc:creator>Karl</dc:creator>
		<pubDate>Fri, 21 Sep 2007 16:51:12 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/589-want-to-try-living-in-vim.html#comment-1741</guid>
		<description>Probably you will find my cheatsheet helpful:
http://karl-voit.at/vim-emacs-cheatsheet_of_freezing_hell.txt

I also learned with the emacs and switched over to vim a year ago.

Short summary: emacs is the best for LaTeX editing (using AUCTeX and RefTeX) but everywhere else, I do prefer vim - not at least because I hate LISP :-)</description>
		<content:encoded><![CDATA[<p>Probably you will find my cheatsheet helpful:<br />
<a href="http://karl-voit.at/vim-emacs-cheatsheet_of_freezing_hell.txt" rel="nofollow">http://karl-voit.at/vim-emacs-cheatsheet_of_freezing_hell.txt</a></p>
<p>I also learned with the emacs and switched over to vim a year ago.</p>
<p>Short summary: emacs is the best for LaTeX editing (using AUCTeX and RefTeX) but everywhere else, I do prefer vim &#8211; not at least because I hate LISP :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ricardo</title>
		<link>http://changelog.complete.org/archives/589-want-to-try-living-in-vim/comment-page-1#comment-1429</link>
		<dc:creator>ricardo</dc:creator>
		<pubDate>Mon, 12 Mar 2007 20:16:26 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/589-want-to-try-living-in-vim.html#comment-1429</guid>
		<description>for setting flags based on filetype i have this in my .vimrc:
autocmd FileType c set autoindent cindent shiftwidth=8 ts=8 foldmethod=indent
autocmd FileType python set nocindent shiftwidth=4 ts=4 foldmethod=indent

and so on. you&#039;ll probably need to have
filetype on
filetype indent on
filetype plugin on

for this to work. btw, you can also have settings based on filename:
autocmd BufRead admin.log* set expandtab

for having multiple open files, tabs are really useful (:tabnew file). you can try this:
https://wiki.ncl.cs.columbia.edu/wiki/index.php/Vim_awesomeness#using_tabs
for a way to make them look nice (there may be a better way now, i haven&#039;t checked in a while)</description>
		<content:encoded><![CDATA[<p>for setting flags based on filetype i have this in my .vimrc:<br />
autocmd FileType c set autoindent cindent shiftwidth=8 ts=8 foldmethod=indent<br />
autocmd FileType python set nocindent shiftwidth=4 ts=4 foldmethod=indent</p>
<p>and so on. you&#8217;ll probably need to have<br />
filetype on<br />
filetype indent on<br />
filetype plugin on</p>
<p>for this to work. btw, you can also have settings based on filename:<br />
autocmd BufRead admin.log* set expandtab</p>
<p>for having multiple open files, tabs are really useful (:tabnew file). you can try this:<br />
<a href="https://wiki.ncl.cs.columbia.edu/wiki/index.php/Vim_awesomeness#using_tabs" rel="nofollow">https://wiki.ncl.cs.columbia.edu/wiki/index.php/Vim_awesomeness#using_tabs</a><br />
for a way to make them look nice (there may be a better way now, i haven&#8217;t checked in a while)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Ekstrand</title>
		<link>http://changelog.complete.org/archives/589-want-to-try-living-in-vim/comment-page-1#comment-1428</link>
		<dc:creator>Michael Ekstrand</dc:creator>
		<pubDate>Sat, 10 Mar 2007 19:00:22 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/589-want-to-try-living-in-vim.html#comment-1428</guid>
		<description>Debian changelog: as others have said, &quot;set nofoldenable&quot;.  Put &quot;setlocal nofoldenable&quot; in ~/.vim/ftplugin/debchangelog.vim to apply that setting only to Debian changelogs.

Editing other files: do &quot;:help buffers&quot;, there&#039;s an option to keep old buffers around at which point &quot;:e&quot; will be what you want.  Add the BufferExplorer plugin from vim.org, and you&#039;ll have a lean, mean editing machine (BufferExplorer gives you a list of open buffers when you hit \be).</description>
		<content:encoded><![CDATA[<p>Debian changelog: as others have said, &#8220;set nofoldenable&#8221;.  Put &#8220;setlocal nofoldenable&#8221; in ~/.vim/ftplugin/debchangelog.vim to apply that setting only to Debian changelogs.</p>
<p>Editing other files: do &#8220;:help buffers&#8221;, there&#8217;s an option to keep old buffers around at which point &#8220;:e&#8221; will be what you want.  Add the BufferExplorer plugin from vim.org, and you&#8217;ll have a lean, mean editing machine (BufferExplorer gives you a list of open buffers when you hit \be).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: petekaz</title>
		<link>http://changelog.complete.org/archives/589-want-to-try-living-in-vim/comment-page-1#comment-1427</link>
		<dc:creator>petekaz</dc:creator>
		<pubDate>Fri, 09 Mar 2007 13:09:01 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/589-want-to-try-living-in-vim.html#comment-1427</guid>
		<description>You can make a set of configurations only applicable to a particular language by using a filetype plugin.  You can load plugins, indentation, and syntax rules based on file type.  See :help filetype for more details.

In summary though, this command enables filetype detection of indentation and plugins:

  filetype plugin indent on

Then, you can create the following directory structure in your $HOME:

.vim/indent/
.vim/ftplugin/

Then say you wanted to tweak the indentation rules used for shell scripting, you would drop a file called &#039;sh.vim&#039; in the indentation directory.  Likewise, if you had some specific feature of vim you wanted enable only when editing sh files, you could add &#039;sh.vim&#039; to the ftplugin directory.

Pete</description>
		<content:encoded><![CDATA[<p>You can make a set of configurations only applicable to a particular language by using a filetype plugin.  You can load plugins, indentation, and syntax rules based on file type.  See :help filetype for more details.</p>
<p>In summary though, this command enables filetype detection of indentation and plugins:</p>
<p>  filetype plugin indent on</p>
<p>Then, you can create the following directory structure in your $HOME:</p>
<p>.vim/indent/<br />
.vim/ftplugin/</p>
<p>Then say you wanted to tweak the indentation rules used for shell scripting, you would drop a file called &#8216;sh.vim&#8217; in the indentation directory.  Likewise, if you had some specific feature of vim you wanted enable only when editing sh files, you could add &#8216;sh.vim&#8217; to the ftplugin directory.</p>
<p>Pete</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Igor Stirbu</title>
		<link>http://changelog.complete.org/archives/589-want-to-try-living-in-vim/comment-page-1#comment-1426</link>
		<dc:creator>Igor Stirbu</dc:creator>
		<pubDate>Fri, 09 Mar 2007 10:28:15 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/589-want-to-try-living-in-vim.html#comment-1426</guid>
		<description>After reading the vim tutorial suggested by Eddy Petrisor, you could take a look at some .vimrc posted on the web to see what you would most likely want to have in your .vimrc. Here is a nice one: http://www.hermann-uwe.de/files/vimrc but  read the help for commands before adding  them. Happy vimming!</description>
		<content:encoded><![CDATA[<p>After reading the vim tutorial suggested by Eddy Petrisor, you could take a look at some .vimrc posted on the web to see what you would most likely want to have in your .vimrc. Here is a nice one: <a href="http://www.hermann-uwe.de/files/vimrc" rel="nofollow">http://www.hermann-uwe.de/files/vimrc</a> but  read the help for commands before adding  them. Happy vimming!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://changelog.complete.org/archives/589-want-to-try-living-in-vim/comment-page-1#comment-1425</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Fri, 09 Mar 2007 09:36:46 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/589-want-to-try-living-in-vim.html#comment-1425</guid>
		<description>set hidden
help hidden</description>
		<content:encoded><![CDATA[<p>set hidden<br />
help hidden</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: i5513</title>
		<link>http://changelog.complete.org/archives/589-want-to-try-living-in-vim/comment-page-1#comment-1424</link>
		<dc:creator>i5513</dc:creator>
		<pubDate>Fri, 09 Mar 2007 09:33:12 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/589-want-to-try-living-in-vim.html#comment-1424</guid>
		<description>Take a look at
 /usr/share/doc/mercurial/examples/vim/</description>
		<content:encoded><![CDATA[<p>Take a look at<br />
 /usr/share/doc/mercurial/examples/vim/</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eddy Petrisor</title>
		<link>http://changelog.complete.org/archives/589-want-to-try-living-in-vim/comment-page-1#comment-1423</link>
		<dc:creator>Eddy Petrisor</dc:creator>
		<pubDate>Fri, 09 Mar 2007 08:58:47 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/589-want-to-try-living-in-vim.html#comment-1423</guid>
		<description>John, many of your questions are answered in the (what I like to call) best dive-into-vim tutorial:

[url]http://www.vi-improved.org/tutorial.php[/url]</description>
		<content:encoded><![CDATA[<p>John, many of your questions are answered in the (what I like to call) best dive-into-vim tutorial:</p>
<p>[url]http://www.vi-improved.org/tutorial.php[/url]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonas</title>
		<link>http://changelog.complete.org/archives/589-want-to-try-living-in-vim/comment-page-1#comment-1422</link>
		<dc:creator>Jonas</dc:creator>
		<pubDate>Fri, 09 Mar 2007 08:50:29 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/589-want-to-try-living-in-vim.html#comment-1422</guid>
		<description>Being able to edit another file and not saving the buffer you are currently in put an ! after the command you use to change buffer. This works for me:
vim three different files
[write something]
:b! different
[write something else]
:b! three
and the stuff i wrote in file three is still there.</description>
		<content:encoded><![CDATA[<p>Being able to edit another file and not saving the buffer you are currently in put an ! after the command you use to change buffer. This works for me:<br />
vim three different files<br />
[write something]<br />
:b! different<br />
[write something else]<br />
:b! three<br />
and the stuff i wrote in file three is still there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ivan Tarasov</title>
		<link>http://changelog.complete.org/archives/589-want-to-try-living-in-vim/comment-page-1#comment-1421</link>
		<dc:creator>Ivan Tarasov</dc:creator>
		<pubDate>Fri, 09 Mar 2007 08:34:54 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/589-want-to-try-living-in-vim.html#comment-1421</guid>
		<description># Turn on or off autoindent, syntax highlighting, etc. in various languages (really, I want to set global defaults for all of them)

:set noai
:set nocin
:set nosi

and be sure to read
:help ai
:help cin
:help &#039;si&#039;

# Be able to edit another file without closing or saving the first (:e doesn&#039;t seem to do what I want)

If you mean that you want to forfeit all your changes and start editing another file, try

:e! &lt;another-file&gt;

If you want to split the window and edit the files in parallel, try

:sp &lt;another-file&gt;
or
:vert sp &lt;another-file&gt;

When you start feeling comfortable, you might want to look at this page: &lt;http://www.rayninfo.co.uk/vimtips.html&gt;, these tips are great, even for hardcore vimmers.

(and be sure to take a look at the corresponding help pages, there are lots of useful things you might want to know)</description>
		<content:encoded><![CDATA[<p># Turn on or off autoindent, syntax highlighting, etc. in various languages (really, I want to set global defaults for all of them)</p>
<p>:set noai<br />
:set nocin<br />
:set nosi</p>
<p>and be sure to read<br />
:help ai<br />
:help cin<br />
:help &#8216;si&#8217;</p>
<p># Be able to edit another file without closing or saving the first (:e doesn&#8217;t seem to do what I want)</p>
<p>If you mean that you want to forfeit all your changes and start editing another file, try</p>
<p>:e! <another -file></p>
<p>If you want to split the window and edit the files in parallel, try</p>
<p>:sp </another><another -file><br />
or<br />
:vert sp </another><another -file></p>
<p>When you start feeling comfortable, you might want to look at this page: <http: //www.rayninfo.co.uk/vimtips.html>, these tips are great, even for hardcore vimmers.</p>
<p>(and be sure to take a look at the corresponding help pages, there are lots of useful things you might want to know)</http:></another></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tonfa</title>
		<link>http://changelog.complete.org/archives/589-want-to-try-living-in-vim/comment-page-1#comment-1420</link>
		<dc:creator>tonfa</dc:creator>
		<pubDate>Fri, 09 Mar 2007 08:18:18 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/589-want-to-try-living-in-vim.html#comment-1420</guid>
		<description>Hum I meant put it in vimrc off course :)</description>
		<content:encoded><![CDATA[<p>Hum I meant put it in vimrc off course :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tonfa</title>
		<link>http://changelog.complete.org/archives/589-want-to-try-living-in-vim/comment-page-1#comment-1419</link>
		<dc:creator>tonfa</dc:creator>
		<pubDate>Fri, 09 Mar 2007 08:15:18 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/589-want-to-try-living-in-vim.html#comment-1419</guid>
		<description>For mercurial just set $EDITOR to vim, the hgmerge script will launch vimdiff on merge automatically.

For the syntax highlight for example for python, put the following in hgrc:
au FileType python set syntax=off</description>
		<content:encoded><![CDATA[<p>For mercurial just set $EDITOR to vim, the hgmerge script will launch vimdiff on merge automatically.</p>
<p>For the syntax highlight for example for python, put the following in hgrc:<br />
au FileType python set syntax=off</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: i5513</title>
		<link>http://changelog.complete.org/archives/589-want-to-try-living-in-vim/comment-page-1#comment-1418</link>
		<dc:creator>i5513</dc:creator>
		<pubDate>Fri, 09 Mar 2007 07:36:27 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/589-want-to-try-living-in-vim.html#comment-1418</guid>
		<description>why don&#039;t you try:
:help folding 
:help autoindent
:help syntax
:help tabs
:help split
:help window

And not sure for mercurial see at:
http://www.vim.org/scripts/script.php?script_id=1293</description>
		<content:encoded><![CDATA[<p>why don&#8217;t you try:<br />
:help folding<br />
:help autoindent<br />
:help syntax<br />
:help tabs<br />
:help split<br />
:help window</p>
<p>And not sure for mercurial see at:<br />
<a href="http://www.vim.org/scripts/script.php?script_id=1293" rel="nofollow">http://www.vim.org/scripts/script.php?script_id=1293</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: romain</title>
		<link>http://changelog.complete.org/archives/589-want-to-try-living-in-vim/comment-page-1#comment-1417</link>
		<dc:creator>romain</dc:creator>
		<pubDate>Fri, 09 Mar 2007 07:12:44 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/589-want-to-try-living-in-vim.html#comment-1417</guid>
		<description>Why?!</description>
		<content:encoded><![CDATA[<p>Why?!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Risto Saarelma</title>
		<link>http://changelog.complete.org/archives/589-want-to-try-living-in-vim/comment-page-1#comment-1416</link>
		<dc:creator>Risto Saarelma</dc:creator>
		<pubDate>Fri, 09 Mar 2007 07:07:12 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/589-want-to-try-living-in-vim.html#comment-1416</guid>
		<description>Using :new or :split will halve the screen space available, which might not be what you want if you have a small screen. If you have Vim version 7 or above, you can also use tabs. Say &quot;:tabe [newfile]&quot; to open the new file in a new tab. See &quot;:h tabpage&quot; for more info on tabs.</description>
		<content:encoded><![CDATA[<p>Using :new or :split will halve the screen space available, which might not be what you want if you have a small screen. If you have Vim version 7 or above, you can also use tabs. Say &#8220;:tabe [newfile]&#8221; to open the new file in a new tab. See &#8220;:h tabpage&#8221; for more info on tabs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian Hergert</title>
		<link>http://changelog.complete.org/archives/589-want-to-try-living-in-vim/comment-page-1#comment-1415</link>
		<dc:creator>Christian Hergert</dc:creator>
		<pubDate>Fri, 09 Mar 2007 06:58:10 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/589-want-to-try-living-in-vim.html#comment-1415</guid>
		<description>&gt; Turn on or off autoindent, syntax highlighting, etc. in various languages (really, I want to set global defaults for all of them)

	Generically, :set syntax and :set syntax=off. You can set specific languages such as :set syntax=python. You probably know this though, and I&#039;m afraid I cannot be of much help on how to do a set of actions based on filetype.

	To turn off auto indent, just :set noai. Again, not sure on how to have preset contexts based on filetypes.

&gt; Be able to edit another file without closing or saving the first (:e doesn&#039;t seem to do what I want)

	:split file.c will split the screen horizontally so you can look and edit multiple files at once. Use CTRL+W W to switch between buffers. You can also do a vertical split with :vert split otherfile.c.

&gt; Integrate it with Mercurial and Darcs

	I set my merge to vimdiff in .hgrc. As for ChangeLog&#039;s, I usually just add a new date line and :r! hg st to enter the status of my mercurial branch.

Cheers, and good luck!</description>
		<content:encoded><![CDATA[<p>> Turn on or off autoindent, syntax highlighting, etc. in various languages (really, I want to set global defaults for all of them)</p>
<p>	Generically, :set syntax and :set syntax=off. You can set specific languages such as :set syntax=python. You probably know this though, and I&#8217;m afraid I cannot be of much help on how to do a set of actions based on filetype.</p>
<p>	To turn off auto indent, just :set noai. Again, not sure on how to have preset contexts based on filetypes.</p>
<p>> Be able to edit another file without closing or saving the first (:e doesn&#8217;t seem to do what I want)</p>
<p>	:split file.c will split the screen horizontally so you can look and edit multiple files at once. Use CTRL+W W to switch between buffers. You can also do a vertical split with :vert split otherfile.c.</p>
<p>> Integrate it with Mercurial and Darcs</p>
<p>	I set my merge to vimdiff in .hgrc. As for ChangeLog&#8217;s, I usually just add a new date line and :r! hg st to enter the status of my mercurial branch.</p>
<p>Cheers, and good luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Helmut Grohne</title>
		<link>http://changelog.complete.org/archives/589-want-to-try-living-in-vim/comment-page-1#comment-1414</link>
		<dc:creator>Helmut Grohne</dc:creator>
		<pubDate>Fri, 09 Mar 2007 05:59:45 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/589-want-to-try-living-in-vim.html#comment-1414</guid>
		<description>:set nofoldenable &quot; will expand your chanelog

Do you want :new instead of :e?

Hope that helps

Helmut</description>
		<content:encoded><![CDATA[<p>:set nofoldenable &#8221; will expand your chanelog</p>
<p>Do you want :new instead of :e?</p>
<p>Hope that helps</p>
<p>Helmut</p>
]]></content:encoded>
	</item>
</channel>
</rss>

