| Age | Commit message (Collapse) | Author |
|---|
|
This adds a trailing comma when using ArgWrap. Go requires trailing
commas, otherwise it reports compilation errors.
|
|
I've been keeping a daily to-do list. Every day, I copy yesterday's
entry and use it as today's with some modifications. Add a mapping to
automate copying the previous day's entry.
|
|
|
|
The JavaScript plugin I'm using does an okay job syntax highlighting
TypeScript, but some identifiers don't get highlighted.
Now that I'm doing a project in TypeScript, it's nice to have everything
highlighted correctly.
|
|
After upgrading to Vim 8.2, an underline was added to the line number of
the current line. Remove this with `CursorLineNr` to restore the look
from before the upgrade.
|
|
|
|
Makes it easier to reformat plain text tables.
|
|
Make it easier to write with typographers' quotes.
Depends on 'vim-textobj-user'.
|
|
The import path was renamed.
|
|
This plugin (specifically the `autoload/todo.vim` file) was colliding
with the 'vim-twodo' plugin, which uses the same file name.
Rename this plugin to prevent name conflicts.
|
|
These are by default highlighted as `Ignore`, which makes them the same
colour as finished and deleted to-dos. Set them to a light grey colour
to make them more readable.
|
|
Includes fixes and useful new features.
|
|
Previously, if the cursor was on a commit line and not at the start of
the line, the `[[` command would move to the start of the current line:
commit 7a06e3db5d7a47a05558dd6557f23e665cc26c39
^
*[[*
commit 7a06e3db5d7a47a05558dd6557f23e665cc26c39
^
This change causes the cursor to move correctly to the previous commit.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Add a plugin with mappings to move to the next and previous TODO.
Needs some cleanup and count support.
|
|
|
|
Analogue to `<leader>cf`, which copies the relative path.
|
|
|
|
Got to be too annoying.
|
|
Use `z<C-^>` to swap between test and implementation files. Gives me a
faster way to navigate.
|
|
Since I turned `gopls` off, vim-go complains when I try to use a "go to
definition" mapping. Turn off vim-go's overrides so I can use ctags,
which is much faster than any of the Go tools.
|
|
Enable extra mappings, text objects, etc. provided by vim-go. Wanted
function scoped motions and text objects, and this was the easy way to
get them.
|
|
The `gopls` tool is super slow and eats up way too many computing
resources.
|
|
This includes a change that allows `gopls` to be disabled:
https://github.com/fatih/vim-go/commit/e3a0e1ead2c14aa27d1d34950c0c43a7b296e368
|
|
|
|
A command that opens the Jira ticket ID cWORD in the browser.
|
|
|
|
* Move functions into autoload
* Remove unused `s:Activate()` and `s:Deactivate()`. These were
development ideas.
* Add a load guard
|
|
A mapping that toggles <Space> to insert '\ ', automatically escaping
spaces when entering file names (such as when creating files with spaces
in their names).
Working, but I now need to clean up the code.
|
|
After trying a few different approaches, finally settled on a mapping
implementation for `c#` that seems to work both at the start and in the
middle of a word.
Previously, as the TODO on line 1 indicates, if the cursor was on the
start of the word, we'd move to the previous match using `c#`. However,
if the cursor was in the middle of the word, `c#` would move to the
start of the word, when it should instead move to the previous match.
First tried to solve the movement problem using `search()`. Managed to
find a formula that did what I wanted, but search highlighting isn't
applied when searching within functions. This function (in particular
the 'z' flag) allows us to move to the previous match even when starting
in the middle of the word:
call search('\C' . expand('<cword>'), 'bz')<CR>
I then tried an <expr> mapping against a function that would call:
call search('\<', 'bc')
first to move to the start of the word (even when already on the start
of the word), then return the `?...` command to run the search for the
previous match. This, however, didn't work because the above mentioned
`search()` call wasn't part of the <expr> mapping, and it's likely the
search was undone, similar to what I encountered next.
I then tried to run an `execute 'normal! ?...'` command to run the
search, preceded still by the aforementioned `search()` call to move to
the beginning of the word. This did not work because it turns out that
searches in a function are undone when that function returns:
:h function-search-undo
This behaviour is also the likely reason why my `search()` + <expr>
function didn't work.
Finally, tried an <expr> mapping containing both the `search()` call to
move to the beginning of the word and the `?...` command to search for
the previous match (all returned in the <expr> string). Once I got the
syntax right, this seems to do exactly what I want.
Left the in-between code states for reference. I'll be cleaning those up
later.
|
|
The printed commands were distracting.
|
|
Enable project search within Vim using Ripgrep.
|
|
Mappings for case sensitive versions # and *. Not completely figured out
yet.
|
|
We already have an n_<leader>w mapping. This new one gives us the
ability to refine the search term to include more than a single word.
now we can include multiple words and punctuation in searches.
|
|
After reading Drew Neil's Follow My Leader again
(http://vimcasts.org/blog/2014/02/follow-my-leader/), I discovered this
issue in which Tim Pope suggests mappings for the SplitJoin plugin:
https://github.com/AndrewRadev/splitjoin.vim/issues/14#issuecomment-9666431
This inspired my to add a mapping for `ArgWrap`. I decided not to before
because `:ar<Tab><Enter>` seemed like it wasn't much effort to type.
But, why not make this a touch quicker?
At first I considered `cJ`, which is available:
nnoremap cJ :ArgWrap<cr>
However, in the aforementioned issue, Pope suggests `gS` as being a free
lhs sequence, which seems nicer.
|
|
Recent Vims have a built-in JSON syntax plugin which is a little easier
to read than the JavaScript highlighting. Use the built-in one on Vim 8
and higher.
|
|
Add a shortcut to quickly insert the UFO ticket folder path at the
command line to save me the trouble of having to type & complete it
manually.
|
|
Add bindings to insert `debugger` statements in JavaScript.
|
|
Omaps for `[[` and `]]` commit motion commands.
|
|
An ftplugin that provides `[[` and `]]` mappings to move between commits
in `git log` output.
|
|
Now that I effectively removed the `checktime` augroup in
cc86bdf4af5212a3b2a7960e65c402eac71091c1, this is no longer necessary.
Also, it errors because `checktime` no longer exists.
|
|
|
|
|
|
Mappings for JavaScript files that add and remove the
`no-debugger: warn` rule to `.eslintrc`.
|
|
Use `s` to wrap text in a GitHub suggestion.
Before:
Text
After:
``` suggestion
Text
```
|
