Skip to content

Issues: arizvisa/vim-incpy

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

6 Open 12 Closed
6 Open 12 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

E605: Exception not caught: Unable to determine basepath from script (during incpy#LoadPlugin) bug neovim specific to the neovim fork of vim
#30 opened Nov 26, 2024 by arizvisa
@arizvisa
Refactor the plugin and its autoload interface to replace script-local functions with autoload-friendlier ones. enhancement
#29 opened Nov 26, 2024 by arizvisa
@arizvisa
Exposing the configuration of the plugin's keybindings using the "<Plug>" key name. enhancement
#28 opened Nov 26, 2024 by arizvisa
@arizvisa
E704: Funcref variable name must start with a capital (during incpy#SetupOptions). bug
#27 opened Nov 26, 2024 by arizvisa
@arizvisa
Tracking blocks of code that have been previously loaded into the interpreter enhancement
#21 opened Oct 17, 2024 by arizvisa
@arizvisa
Code folding in the output window for each selection submitted to an interpreter and its output. enhancement
#13 opened Oct 2, 2024 by arizvisa
1
ProTip! Exclude everything labeled bug with -label:bug.