junegunn / junegunn/vim-peekaboo

cmd height changed to maximum

Open
#74 5 comments 12 reactions 0 assignees View on GitHub
Dominant language
Vim Script
Stars
1.2k
Forks
42
PR merge metrics
No merged PRs in 30d

Description

I can't figure out which plugin caused the issue, with minimum config it's ok, but with plugins enabled it shows the error.

I think the plugins related are peekaboo, vim-surround, vim-airline.

steps to reproduce:

1. record a micro like so: `qqf=ysiw"j0q`
`qq` record macro `q`
`f=` move to `=`
`ysiw"` add around a word `"`
`j0q` move to next line and to the beginning and end macro
2. keep applying `@q`
3. when there is a blank line, the error shows

screenshot before pressing `@q`:
![image](https://user-images.githubusercontent.com/360983/87886996-1d224600-ca19-11ea-99e1-84692caa2b77.png)

screenshot after bug
![image](https://user-images.githubusercontent.com/360983/87886975-ff54e100-ca18-11ea-81df-f086f374dd0b.png)

at this point I had to resize the windows vertically to get it back,

set verbosefile=filename.txt
set verbose=9

relevant part of the log:

```
Executing BufEnter Autocommands for "*"
autocommand if g:repeat_tick == 0|let g:repeat_tick = b:changedtick|endif

Error detected while processing function peekaboo#aboo[76]..140_close:
line 1:
E939: Positive count required: bd 0
airline: group: airline_error already done, skipping
airline: group: airline_error_bold already done, skipping
airline: group: airline_error_red already done, skipping
airline: group: airline_c1_to_airline_x already done, skipping
airline: group: airline_c1_to_airline_x_bold already done, skipping
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the issue by repeatedly applying the recorded `@q` macro until a blank line is reached, then inspect the verbose log around `peekaboo#aboo` and `140_close`, especially the `E939: Positive count required: bd 0` error. Done means the command height remains usable and the reproduction no longer produces this error with the reported plugins enabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
vim
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.