Yilin Yang

Hi @mterwill! Sorry about the hugely delayed response. Yup, a "Scramble Queue" button (plus "Are you sure?" confirmation dialog, etc.) would work for our needs!

I don't think that I would be able to, unfortunately, with everything that's going on. 😢 That might change over the next several months (and would probably change by early...

Hi, sorry for the delay. Reopening this issue; I'm open to working on this.

I've been thinking about a design for this. Rather than a small pop-up window at the cursor, I'd like to add the option to show the whole markbar (or the...

Did some debugging in nvim with vim-markbar commit b6b43ca3b91d516d25b92f6d42e51dd13634ffb1 by: - Adding `let g:foo = input('pause until something is entered')` to `.travis_vimrc`, to make vim pause before running Vader tests,...

Always using the same name for the variable storing `redir =>` output is a quick-and-dirty fix for the error message. The underlying issue in (neo)vim still exists, but it doesn't...

Repeated my debugging process from earlier, but with vim `v8.2.5157` instead of neovim. 1. Checked out commit b6b43ca3b91d516d25b92f6d42e51dd13634ffb1 of vim-markbar, 2. Added `let g:foo = input('pause until something is entered')`...

Hi, sorry for the delay. When you do this, does the markbar still open eventually (after a second or two) even when you don't press any keys? My first thought...

Closing for inactivity. Please reply if this is still an issue.

Managed to set up a [Docker image](https://hub.docker.com/repository/docker/yiliny/vim-markbar-tester/general) that aggregates binaries for vim v8.1.0039 and neovim v0.3.4 so that developers can (in principle) perform a thorough Travis CI-esque test run on...