This swap over should have really been tested more before pushing into
mainline. This is hopefully the last one we need to fix.
When I was playing around with the plugin I used a `git clone` this have
it the name of the repo "tmux" that was not very helpful when looking at
the plugins. I then renamed it when adding it to the dotfiles install.
However, I never changed the name in the config to load the plugin from
a different place.
When pushing your stack we show all the branches we have pushed to with
a compare link to github. When we create a PR the compare link is no
longer relevant. Now we will show a link to the PR that is associated
with that branch.
When you are in a buffer sometimes you want to do a search and replace
but preserve the case. For example if we have the following code.
```rust
let some_struct = SomeStruct::new();
```
if we want to rename this to `another_struct` we can call dev case and
it will search and replace preserving the case. We can run the following
command.
```
:S some_struct another_struct
```
This will replace the above code so we will be left with
```rust
let another_struct = AnotherStruct::new();
```
This plugin handles calling the cli tool and displaying an in place
preview of the change so you can see exactly what you will be changing.
It uses the `S` custom command so it feels similar to the built in `s`
Substitute command.
This is moves everything I can think of. A lot of the things I use have
this built in. The vim and tmux themes has been added so the place I
spend all my time looks nice.
This add a pattern for all lua files that will go to the corresponding
spec files. I don't think this will work on all the different projects
but, its a good start. There may need to be some tweaking to make it
work in vim plugins.
There have been some changes in the cspell config upstream to fix issues
in the cspell cli. These are mainly around the parsing of the output.
The only things my changes are adding in the file type and applying my
config file. They are only in the command not the parser.
Now we are using the upstream config and adding the extra params I need
rather than having to maintain a completely override.
This is causing issues with losing the cursor, you then need to move the
cursor over another window to get it back.
On Gnome it is also not picked up but the window manager. You cannot
then using tools like wmctrl to reposition and resize it.
When running commit, any new file that has been created dose not show up
ready to be committed. I am running commit in interactive mode so it
dose not get committed automatically. I can then choose if I want to
actually commit the file
Previously we were defining what ones we want to install. Now we are say
we want to install the grammar when we go to a file. If we don't have
that grammar installed then we will install it then
When writing tests with busted they use some other globals that you need
to tell you lsp about. I already have this for when I'm working on the
nvim config and configz.
Now that I have mostly moved over to sapling, rg dose not ignore git
files by default. When searching in vim it would search in the
node_modules by default. As you can imagine this took for ever.
Now we are passing the `--no-require-git` flag so it will ignore any
file / dirs that are in any .gitignore by default.
When using wezterm on wayland the gnome titlebar dose not get used. The
coloring of this is dark by default and dose not look good with a light
background.
Going forward I would like to configure this to adapt to the system
light or dark settings.
When running other log command the template I had setup in `sl` was not
getting used. This has now been put into the config so its the default
template for any log command.
This also adds a quick alias to switch to another head. When reviewing
pull requests locally this helps quickly switch between heads.
Change the included commits to be the full tree, no matter where you are
on the stack. There is the graphnode to indicate where you are with a
`@`.
Change the color of public commits so you can easily see what are your
commits on the stack. This makes moving around and rebasing easter when
you can see when your last public commit it.
Remove the hard 40 commit limit. Now we are getting the last 40 public
commits plus the commits on your stack
When we are in a sapling repo `gh pr checkout` will not work. If this is
the case we wil need to export the PRR_NUMBER so we can skip getting the
PR number. Working with prr and sapling comes with following limitation.
You can only use the branch name. When git you can use the pr number,
url or the branch. Unfortunately so we can checkout we will need to use
the branch name.
We are now adding lints test that disable async tests that do not use
await in them. I am by far the biggest offender for this and this is one
of the main reasons. Now any test I write will be synchronous by default
until I need it to be async.
In some of the github fonts there are some glyphs now supported, they
are mainly getting used as icons in the vim completion ui.
Now we are not getting any system messages for this it has become quite
annoying.
The ollama plugin was using some APIs that are not yet available in nvim
stable. Now we are using the older APIs we can use this on other
versions of nvim.
The `vim.api.nvim_buf_set_text` does not take some parameters as `-1` to
add text to the end of the line. Now we are getting the text on the last
line adding the new text to it, then replacing the last line.
When running rmv on other linux installes other than Ubuntu its better
to install rmv for the user. This then gets installed in `~/.rvm`.
This now sets up the path so we can use rmv no matter what distro we are
on.
This enhancement includes key mappings designed to improve code folding
in Vim. One of these mappings involves a double leader, which
efficiently toggles the current fold. Additionally, another mapping
utilizes the square bracket convention for seamless navigation between
folds, employing the mnemonic "fold."
Consideration was given to the potential conflict between the `f` key
and "function." After thoughtful deliberation, the decision was made to
use LSP for navigating around functions.
The implementation is currently integrated with prr to narrow the focus
of differentials to a single hunk. This refinement significantly
enhances the manageability of reviewing large pull requests.