This repository was archived by the owner on Sep 15, 2026. It is now read-only.
Repository navigation
Releases: jpetrie/vim-counterpoint
Releases · jpetrie/vim-counterpoint
Release list
v1.7
v1.6
g:counterpoint_include_pathcan be enabled to let Counterpoint parse vim's internalpathoption for search paths.- Absolute paths defined in
g:counterpoint_search_pathswill be searched correctly. - Fixed a bug that caused paths containing spaces to confuse (and break) Counterpoint.
- Fixed a bug that caused errors when using Counterpoint in unnamed buffers, such as the default empty buffer you get when starting Vim.
- Fixed a bug that caused errors when using Counterpoint with
g:counterpoint_include_listedenabled and trying to cycle counterparts while an unnamed buffer (such as the default empty buffer) was in the buffer list.
v1.5
- Fixed a bug preventing
g:counterpoint_depthfrom being correctly respected when scanning listed buffers (wheng:counterpoint_include_listedis set to 1). - Fixed a bug that occasionally caused erratic behavior on Windows when cycling counterparts not contained under the current working directory.
v1.4
- Added
g:counterpoint_include_listed, which can be set to 1 to allow Counterpoint to examine the listed buffers when choosing a counterpart (this really should have been included in version 1.3). Reverted the default behavior of Counterpoint to not look at listed buffers.
v1.3
- Listed buffers are included in the set of potential counterparts.
nofilebuffers are matched using their name as displayed byls, regular buffers have their names expanded to complete file paths. - Cycling counterparts will hit the disk half as often.
v1.2
- Added the ability to configure Counterpoint to prompt you for direct counterpart jumps if the number of available counterparts meets a certain threshold. Disabled by default, see
:help g:counterpoint_prompt_thresholdfor details. - Fixed a bug that caused errors when trying to switch counterparts in an unnamed buffer (such as the default).
v1.1
- Cycling commands can use the postfix bang (
CounterpointNext!) to indicate that they should try to switch to an existing window on the target buffer, if possible. - Cycling commands can take arguments. If present, these arguments will define the command that will be run to edit the target file.
- Broke cycling and computation of the next counterpart into separate functions.
- Counterpoint's code is now delay-loaded via vim's autoload mechanism.