coder / coder/claudecode.nvim

[FEATURE] Multi-line editing in prompt area

Offen
#109 4 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Lua
Sterne
3.1k
Forks
216
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

## Feature Description

When entering a longish prompt, I would like to be able to split the instructions visually over multiple lines.

## Use Case

I believe this will make it easier to work with longer prompts. Example:

Please introduce feature foo. Do this by:
1. meeting requirement bar
2. meeting requirement baz

Is for me easier to read than:

Please introduce feature foo. Do this by: 1. meeting requirement bar 2. meeting requirement baz.

## Proposed Solution

I'm not sure how the prompt area is implemented under the hood, but I could image this either being a buffer that allows multiple lines to be entered (which would also allow more complex editing to be done slightly easier), or I could image that a keybind is introduced (e.g. shift enter) that causes a line break and then the possibility to continue to edit on the next line.

## Alternatives Considered

When copying pasting into the windows, multi line input is supported / can be pasted into the prompt area in the claude code terminal window in neovim, so a potential alternative is to construct prompts outside of the claude code buffer and then past them into the prompt area. This is clunky though, and for longer prompts can lead to the prompt showing that n lines have been pasted, but not showing all these lines (which is useful by itself, but makes this a less desirable alternative solution for me)

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Rechercherichtung

The issue names no files, tests, or entry points, so first locate the prompt-area implementation and review how input, pasted multiline text, and keybindings currently behave. Compare the proposed buffer and Shift-Enter approaches, then define the editing and submission behavior that would make the feature complete.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
lua, neovim
Bereich
cli, devtools
Issue-Typ
Feature
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.