vimtk VS vim-jumpsuite

quickopen is also available as a functionvimtk#quickopen from my vimtk plugin.

The pyperclip library is responsible for a good portion of my productivity. It powers my vimtk vim plugin, which lets you `a` on a line or visual selection, then it copy / pastes that line into the most recently opened terminal, and then returns focus back to gvim (it does require gvim, because I don't know how to differentiate between a terminal where you are executing bash/python and a terminal you are using vim to edit with; if anyone has ideas on how to do this I'd love to know).

Oh, you're in luck because I've actually written this exact plugin, it's called vim-jumpsuite. It is personally one of my special weapons that's becoming completely indispensable for me.

vim-jumpsuite: parses python tracebacks and identifies the most "interesting" part of the stack to create a jump list; despite vim being in the name, the python part of the plug-in is usable with any editors that supports parsing grep/quickfix-style output

Here is link number 1 - Previous text "my"

vim-jumpsuite for creating a quickfix/loclist jumps out of unittest tracebacks

vim-test with lieryan/vim-jumpsuite

For more elaborate cases, I wrote a plugin that summarises python traceback into the quickfix list. vim-jumpsuite is designed to be used when writing unittest/pytest; for each failing test, it'll try to pick the three most important locations that you'll want to jump to. You can also configure certain files/functions to never be picked by vim-jumpsuite.

Plug: one of the most valuable plugin for me are the vim plugin that I wrote myself: lieryan/vim-jumpsuite. It's a plugin to quickly jump to "interesting" line of code from your test suite by converting unittest reports to a Quickfix jumplist. The plugin uses some customizable heuristics to find the lines from tracebacks that are most likely to be most useful to your code.