| Age | Commit message (Collapse) | Author |
|---|
|
Provides syntax highlighting for Prr code review files.
This code was copied from the 'prr' repository
(https://github.com/danobi/prr/) at commit
9b44c3f2d4b79013a00aae82cb59fe63306967ca
(https://github.com/danobi/prr/commit/9b44c3f2d4b79013a00aae82cb59fe63306967ca).
The Vim plugin lives in a subdirectory of the 'prr' repository, which
made it tricky to include as a submodule.
I added GPLv2 license headers based on the license of the Prr project,
however the Vim code seems to indicate it was based on Vim-licensed
code, so I'm not clear on what the actual license is supposed to be.
I'm assuming it's GPL.
|
|
I only use this command in an AODocs context. Today, I decided to change
the path where these temporary files are saved. Since the path now uses
a project-specific path variable, it made sense to move the command into
the project file.
|
|
When the blame window is closed, ensure the wrap setting is restored.
Not sure where `l:wrap` came from, maybe just an oversight on my part.
|
|
Since this plugin is written in Vim9script, it won't work in any earlier
version. Add a guard to prevent the plugin from loading in earlier Vim
versions.
|
|
|
|
Clean up the plugin file and move the bulk of the work to autoload.
|
|
|
|
If the 'xkbswitch' command isn't available, we shouldn't be adding any
autocmds.
|
|
I assumed that I should be removing existing autocmds before adding new
ones. If you ran the `:InsertLayout` command more than once, I didn't
want old autocmds to stick around.
The line was commented out because it fails on the first call to
`:InsertLayout`, since at that point the `insert_layout` augroup doesn't
exist.
On closer inspection, however, it turns out that the old autocmds are
not retained when running `:InsertLayout` subsequent times. Rather, the
newly-defined ones are overwriting the old ones. So we don't need to
worry about removing the old autocmds before adding new ones.
|
|
This allows us to complete the command's keyboard layout identifier
making it easier to select one.
|
|
Add two new commands, `InsertLayout` and `InsertLayoutOff`, which allow
us to activate a different keyboard layout for insert mode and restore
the previous layout when leaving insert wode.
Works reasonably well, but needs a bit of cleaning up now.
|
|
This uses `xkbswitch` to change keyboard layouts on insert enter and
leave. For now it's only a proof of concept.
The plan is to make an `:InsertLayout` command that takes an argument
defining the keyboard layout to use in insert mode. When returning to
normal mode, it should switch back to the previous layout.
This uses https://github.com/myshov/xkbswitch-macosx/.
|
|
Easily complete email addresses from the Mutt aliases file when
composing an email message.
|
|
Add a new `:WChat` command to quickly save temporary files based on a
timestamp. I've been doing this manually to write chat messages but it
occurred to me that it would be nice to save a bit of thought and effort
for this.
|
|
I needed to run `:GoInstallBinaries`, but this failed as I'm using Go
1.18, and the version of Vim-Go I was using installed binaries with
`go get` instead of the new `go install`. This was updated and fixed in
359230b942b3aba79d011aa446bfcf70c12bc217.
|
|
Shows code context including the enclosing function, class, namespace,
etc.
|
|
|
|
A new command that appends MacPorts checksums for a given file.
|
|
Make Common Lisp development more fluid.
|
|
|
|
Create a new 'godoc' filetype that highlights the same as 'go' except
without the character group. This makes Go docs produced by the `go doc`
command more readable.
|
|
I had a problem loading the SWANK server so I thought a plugin update
might fix it. Turns out it was an unrelated path override problem
causing an old Slime/Swank version to be loaded.
|
|
Adds new motion bindings.
|
|
Add a command to insert the current date after point. Saves me a bit of
typing, as well as effort remembering the current date.
|
|
I've been using this locally on one machine since I finished writing the
plugin, but apparently forgot to add it to my .vim.
|
|
Provides syntax highlighting for MacPorts Portfiles.
This code was copied from the 'macports-contrib' repository
(https://github.com/macports/macports-contrib) at commit
513c455d5a902fff2b38edf86abc15c36688bf85
(https://github.com/macports/macports-contrib/tree/513c455d5a902fff2b38edf86abc15c36688bf85).
The Vim plugin lives in a subdirectory of the 'macports-contrib'
repository, so I'd have to include a whole mess of files that don't
relate to Vim if I wanted to add the plugin as a submodule. I'd just as
soon not have to copy the files into my repository tree like this, but
it's better than adding a non-Vim submodule.
Assuming it's okay to add these files to my repository, as the port file
for this plugin describes it as being BSD licensed:
https://github.com/macports/macports-ports/blob/12d7b1597bef875058758c9c587b7593f39a5af1/editors/mpvim/Portfile
Unfortunately, there's no BSD license or copyright notice included in
the plugin code. But I'm going to assume I'm allowed to redistribute it.
|
|
Use Vlime instead of Slimv for a Common Lisp environment.
|
|
Haven't been using this plugin. Recently started a Common Lisp project,
but am going to use Vlime instead, which seems to integrate better with
user configuration.
|
|
Don't change the author for moved lines.
|
|
I was having trouble with slow `<C-p>` completion, and figured out it
was due to the fact that I had about 300 buffers open.
Many of these buffers weren't being actively used, and were just loaded
in from Vim sessions past. When I removed the unloaded buffers,
completion sped up like a whistle.
Thanks to 'sidyll' (https://stackoverflow.com/users/557306/sidyll) on
Stack Overflow for explaining how to get "all" buffer numbers (or at
least all possible buffer numbers up to the highest one open), as well
as the filtering logic:
https://stackoverflow.com/questions/17931507/vimscript-number-of-listed-buffers/17933352#17933352
I leveraged the above to get the buffer numbers of all unloaded buffers,
then delete the buffers by number.
It was originally a temporary command-mode line, but I decided it could
be beneficial to save the code just in case I need it again.
|
|
Adds operator-pending and visual mode mappings.
|
|
|
|
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.
|
|
Makes it easier to reformat plain text tables.
|
|
Make it easier to write with typographers' quotes.
Depends on 'vim-textobj-user'.
|
|
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.
|
|
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.
|
|
This includes a change that allows `gopls` to be disabled:
https://github.com/fatih/vim-go/commit/e3a0e1ead2c14aa27d1d34950c0c43a7b296e368
|
|
|
|
|
|
* 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.
|
