Skip to content

fix: prevent buffer change while parsing#535

Merged
boltlessengineer merged 5 commits intomainfrom
fix/lazy-resolve-vars
Feb 24, 2025
Merged

fix: prevent buffer change while parsing#535
boltlessengineer merged 5 commits intomainfrom
fix/lazy-resolve-vars

Conversation

@boltlessengineer
Copy link
Copy Markdown
Contributor

@boltlessengineer boltlessengineer commented Feb 23, 2025

Closes: #524

Using just current buffer `0` can cause parsing on different buffer.
E.g. user might open different buffer on `vim.ui.input` changing
"current buffer".
Specify the exact buffer instead
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Request with prompt variables crashes when using custom input prompt UI

1 participant