A quick one-key ai modification helper

[Kailian-Jacy]

Motivation

Currently, applying the fully automated AI coder is very unreliable and feasible to be adopted in massive industry production. So I want to integrate my neovim with the lightweighted and highly interactive AI assistance.

Philosophy

• Keep it as simple as possible, evolve it. Add AI technology evolves. Learn from the bit lesson of Avante.
• Minimize the intervention to my usual coding as much as possible since the special intelligence help is not always stable.

Scenerios

• Implement based on pseudocode.
• Fix problem on the basis of comment instruction.
• Provide Hazard Check and Suggestions for the selected code.

To put it simple, just select the region of code, query the artificial intelligence and edit the piece of code.

Demos

• Extmark region shifting.
• Openrouter LLM query.
• Keymaps & configurations.
• Buf local pending modifications.
• Highlight color shifting.
• Floating buffer gathering informations and display.

Features: v0: implementation based on the other plugin

GpRewrite

Finished.

Features: v1: implementation of the core functionality

Just rely on the assumption that we are working on very fast model that we are going to edit in sync mode.

• Interaction and appearance.
  • Marks to indicate the generation working progress
  • Keymaps to stop generation. Keymaps to discard/accept pending changes and retry.
• Core feature: Select, Added and Replacement.
  • Interaction with artificial intelligence model.
  • Templating, prompting, and the result parsing.
• Fault tolerance and timeout control.
  • Timeout configuration.
  • Retry keymap and automatic retry.
• Observability and benchmark.
  • Just set up benchmark mode and gave some test cases to run on.
    • This benchmark should focus on the stability and the capacity of each model following the rules we gave them, rather than how wise or how deep their understanding toward code is.
    • In order to simplify this experiment, instead of using some very complex test cases to benchmark, use some very fixed and easy to understand test cases and compare the results with the correct answers automatically, possibly with git diff.
  • Set a dashboard to display the results.

Feartures: v2

Introduce more facilities about asynchronous and to unleash the potential of using more powerful reasoning models that are more time wasting.

• Interaction and appearance.
  • Picker to operate on edition.
  • Diff mode to select and merge.
  • [Optional] Marker to track the origin to be replaced.
• Floating window to track the progress.
  • Reversing position from the cursor position to the region that edited by LLM.
  • Floating window scrolling display.
• Pending status and resolve.

[Kailian-Jacy]

Async editor

nvim_buf_set_lines.

Rolling sign

local spinner_frames = { "⠋", "⠙", "⠹", "⠸", "⠼", "⠴", "⠦", "⠧", "⠇", "⠏" }
local retry = "⟲"
local pending = "◌"

:sign define MySign text=>> texthl=ErrorMsg
:execute ":sign place 10 line=5 name=MySign"

Use 80-120ms intervals (claude)

Mark region

Wants:
Technically, what I want is just a simple region-based solution. If the addition happens inside the region, just shrink or expand the region. If it happens outside of the region, shift the region accordingly. Are there any similar ones?

Suggested by claude:

local start_mark = vim.api.nvim_buf_set_extmark(0, ns_id, start_row, start_col, {
  end_row = end_row,
  end_col = end_col,
  right_gravity = true,  -- Don't move when text inserted at start position
  end_right_gravity = false,  -- Extend when text inserted at end position
})

  local marks = vim.api.nvim_buf_get_extmarks(
    bufnr,
    ns_id,
    0,
    -1,
    { details = true }
  )

--- Stop
local function clear_cold_regions(bufnr)
  bufnr = bufnr or 0
  stop_spinner(bufnr)
  vim.api.nvim_buf_clear_namespace(bufnr, ns_id, 0, -1)
  print("Cold regions cleared")
end

[Kailian-Jacy]

Color marking

TODO: need some way to mark the region being replaced

• possible solution I: signcolumn: scrolling sign. -> too noisy.
• possible solution II: fad/dim/desaturated foreground color + scrolling extmark.
• possible solution III: dim background + scrolling extmark. -> interrupting other bg highlights, conflict with transparency.

Color generation

• Color shift

The best solution to change certain color is to calculate it online...
Now we got

            HighlightedNormal = { bg = "#373461" }

(Saturation down, lightness up).

[Kailian-Jacy]

Possible plugin: gp.nvim

https://github.com/Robitx/gp.nvim

• GpRewrite
• GpImplement

This plugin aims to adapt for different providers serving LLM. It provides sufficient functionality and flexibility, making it easy to be hooked and operate on the LLM's response.

However, there are some missing features:

• The cursor is fixed during generation.
• There's no progress indicator or interruption mechanism for the text generation.
  • Interrupt does exists, but not smooth.
• There's no timeouts or any protection for abnormal requests.
• There's no some other vital features like retry.

Some future limitations:

• Only supports one Implement session per buffer: is_busy