onivim/oni

Broken nvim plugin input

Open

#1,589 opened on Feb 20, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (11,389 stars) (336 forks)batch import
bughelp wantedinsider

Description

I use UltiSnips which asks me which snippet to expand when their are more than one with the same name: 2018-02-20-181201_905x86_scrot

Now this doesn't working anymore and my input is rendered where my cursor was but not forwarded to that input. Must kill Oni.

Contributor guide

Tech stack
typescript
Domain
desktop
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Neovim plugin systemOni input handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
The issue describes a bug where input from UltiSnips is not forwarded correctly in Oni's Neovim integration. Start by examining the input handling code in Oni's Neovim window implementation, likely in files related to the Neovim API or UI layer. Check if there have been any recent changes to the rendering of custom inputs. Reproduce the issue with UltiSnips to isolate the problem. Look for any differences between how Oni handles normal text input versus plugin requested inputs.
Broken nvim plugin input · onivim/oni#1589 | Good First Issue