<feed xmlns='http://www.w3.org/2005/Atom'>
<title>dotvim/vimrc, branch master</title>
<subtitle>My vim configuration</subtitle>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/dotvim/'/>
<entry>
<title>vimrc: Add `[b` and `]b` buffer cycling mappings</title>
<updated>2024-04-05T19:33:47+00:00</updated>
<author>
<name>Teddy Wing</name>
</author>
<published>2024-04-03T21:54:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/dotvim/commit/?id=ff8657a1a50bbbe5ef1fad71f269bca361e53f02'/>
<id>ff8657a1a50bbbe5ef1fad71f269bca361e53f02</id>
<content type='text'>
I've had these on `&lt;leader&gt;k` and `&lt;leader&gt;j` since the early days, but
those mappings no longer feel logical to me. It seems that `[b` and `]b`
are unbound, so I decided to bind these to buffer switching, for the
rare times when I need it.

Eventually I'll probably remove one or the other set depending on what I
end up sticking with.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
I've had these on `&lt;leader&gt;k` and `&lt;leader&gt;j` since the early days, but
those mappings no longer feel logical to me. It seems that `[b` and `]b`
are unbound, so I decided to bind these to buffer switching, for the
rare times when I need it.

Eventually I'll probably remove one or the other set depending on what I
end up sticking with.
</pre>
</div>
</content>
</entry>
<entry>
<title>vimrc: Only turn on 'smoothscroll' if it's available</title>
<updated>2023-09-25T17:27:31+00:00</updated>
<author>
<name>Teddy Wing</name>
</author>
<published>2023-09-25T17:27:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/dotvim/commit/?id=61757534802b493131fdf539a4d08eb77a551493'/>
<id>61757534802b493131fdf539a4d08eb77a551493</id>
<content type='text'>
Keep supporting older versions of Vim.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Keep supporting older versions of Vim.
</pre>
</div>
</content>
</entry>
<entry>
<title>vimrc: Turn on 'smoothscroll'</title>
<updated>2023-09-25T17:22:19+00:00</updated>
<author>
<name>Teddy Wing</name>
</author>
<published>2023-09-25T17:11:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/dotvim/commit/?id=b171b70f2adcde12403f80e9fe762284553e4388'/>
<id>b171b70f2adcde12403f80e9fe762284553e4388</id>
<content type='text'>
I learned about this recently. According to
https://vi.stackexchange.com/questions/11315/visual-scrolling-visual-c-e-and-c-y-across-wrapped-lines/42278#42278
it was added in Vim 9.0.0640.

This allows scrolling within a soft-wrapped line, useful for writing
prose, and very useful for reading files consisting of a single line,
like a big JSON file or minified HTML.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
I learned about this recently. According to
https://vi.stackexchange.com/questions/11315/visual-scrolling-visual-c-e-and-c-y-across-wrapped-lines/42278#42278
it was added in Vim 9.0.0640.

This allows scrolling within a soft-wrapped line, useful for writing
prose, and very useful for reading files consisting of a single line,
like a big JSON file or minified HTML.
</pre>
</div>
</content>
</entry>
<entry>
<title>vimrc: Turn off Vim-Go goimports on save</title>
<updated>2022-08-24T19:24:36+00:00</updated>
<author>
<name>Teddy Wing</name>
</author>
<published>2022-08-24T18:48:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/dotvim/commit/?id=1394a4287b7aa0aa3d89bb2fd66fd77f0d3e15f3'/>
<id>1394a4287b7aa0aa3d89bb2fd66fd77f0d3e15f3</id>
<content type='text'>
The new version of Vim-Go that I upgraded to added a new auto-format on
save hook that runs goimports. Turn if off like we did with its
automatic gofmt.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The new version of Vim-Go that I upgraded to added a new auto-format on
save hook that runs goimports. Turn if off like we did with its
automatic gofmt.
</pre>
</div>
</content>
</entry>
<entry>
<title>vimrc: Add `:Co` command, alias for `:Copy`</title>
<updated>2022-08-20T13:28:56+00:00</updated>
<author>
<name>Teddy Wing</name>
</author>
<published>2022-08-20T13:25:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/dotvim/commit/?id=86646c99e16bdce6b156d6d3433a1251ae7482ac'/>
<id>86646c99e16bdce6b156d6d3433a1251ae7482ac</id>
<content type='text'>
I use this command frequently, and `:Copy` used to tab-complete first
with `:Co&lt;Tab&gt;`, but since I installed the Context.vim plugin, the
latter takes completion precedence. Add this alias to give `:Copy` the
highest precedence.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
I use this command frequently, and `:Copy` used to tab-complete first
with `:Co&lt;Tab&gt;`, but since I installed the Context.vim plugin, the
latter takes completion precedence. Add this alias to give `:Copy` the
highest precedence.
</pre>
</div>
</content>
</entry>
<entry>
<title>vimrc: Add `m,` mapping to save session</title>
<updated>2022-06-28T19:24:54+00:00</updated>
<author>
<name>Teddy Wing</name>
</author>
<published>2022-06-28T17:48:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/dotvim/commit/?id=282cd406e02a54c978003b86977559842434cd93'/>
<id>282cd406e02a54c978003b86977559842434cd93</id>
<content type='text'>
I've been testing this binding as a candidate for a potential
replacement of my existing `&lt;leader&gt;mk` mapping. It's easier on the
hands than the existing one.

Since `,` doesn't seem to be a valid mark location, and it's right next
to the "m" key on a Qwerty keyboard, this seemed like an ideal
combination of keys for a relatively frequent action.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
I've been testing this binding as a candidate for a potential
replacement of my existing `&lt;leader&gt;mk` mapping. It's easier on the
hands than the existing one.

Since `,` doesn't seem to be a valid mark location, and it's right next
to the "m" key on a Qwerty keyboard, this seemed like an ideal
combination of keys for a relatively frequent action.
</pre>
</div>
</content>
</entry>
<entry>
<title>vimrc: Disable context.vim by default</title>
<updated>2022-06-01T19:03:33+00:00</updated>
<author>
<name>Teddy Wing</name>
</author>
<published>2022-06-01T18:40:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/dotvim/commit/?id=e3ec82e56b08d6d0fc9098eb93dcaf121f536904'/>
<id>e3ec82e56b08d6d0fc9098eb93dcaf121f536904</id>
<content type='text'>
Enable it by default in AODocs paths.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Enable it by default in AODocs paths.
</pre>
</div>
</content>
</entry>
<entry>
<title>vimrc: Add `yp` mapping to paste from the "0 register</title>
<updated>2022-06-01T19:03:33+00:00</updated>
<author>
<name>Teddy Wing</name>
</author>
<published>2022-06-01T18:14:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/dotvim/commit/?id=7da6f24af2750e12cae9448847952fa528399539'/>
<id>7da6f24af2750e12cae9448847952fa528399539</id>
<content type='text'>
Makes it easier to search and replace with `n` and visual selection.
Though perhaps `gn` would solve this? Though not in cases where I need
to replace something that's different from the search pattern.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Makes it easier to search and replace with `n` and visual selection.
Though perhaps `gn` would solve this? Though not in cases where I need
to replace something that's different from the search pattern.
</pre>
</div>
</content>
</entry>
<entry>
<title>vimrc: Remove Slimv settings</title>
<updated>2022-05-26T15:29:55+00:00</updated>
<author>
<name>Teddy Wing</name>
</author>
<published>2022-05-25T21:40:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/dotvim/commit/?id=110106795b8d77e27ebd9799cd7b886d78599aac'/>
<id>110106795b8d77e27ebd9799cd7b886d78599aac</id>
<content type='text'>
I removed the Slimv plugin in b0f617dcc33b2207dfb87b899a655f62ecad53ca.
We no longer need these settings.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
I removed the Slimv plugin in b0f617dcc33b2207dfb87b899a655f62ecad53ca.
We no longer need these settings.
</pre>
</div>
</content>
</entry>
<entry>
<title>vimrc: Don't let Paredit change filetype plugin and indent settings</title>
<updated>2022-05-26T15:29:55+00:00</updated>
<author>
<name>Teddy Wing</name>
</author>
<published>2022-05-25T21:37:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/dotvim/commit/?id=f62da435d5b57fadee01ac32ffa08beb4488031f'/>
<id>f62da435d5b57fadee01ac32ffa08beb4488031f</id>
<content type='text'>
Paredit turns filetype indent on globally, messing up all files, not
just Lisp files. Prevent Paredit from changing these settings.

I don't think we really need Paredit's filetype indent as that's already
handled by Vlime.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Paredit turns filetype indent on globally, messing up all files, not
just Lisp files. Prevent Paredit from changing these settings.

I don't think we really need Paredit's filetype indent as that's already
handled by Vlime.
</pre>
</div>
</content>
</entry>
</feed>
