where the above would let me go to definition for locally installed pip packages in my system python.
However, often times library sources are in weird places. This differs user-to-user (e.g., b/c $HOME does) and is dependent on python configuration. For instance, for my recent poetry-based project, the python library sources would be found with:
Obviously, this is all very user and system and language dependent, but if dumb-jump.el were to provide a hook to add include paths dynamically (i.e., after loading a .dumbjump config), then I could add my own elisp logic which could dynamically generate system library paths based on the current buffer. E.g., if the lang is python then my hook could run poetry run python -c 'import site; print(site.getsitepackages())' and add those to the :include config.
dumb-jump looks really cool, thank you for making it!
Often, I'll want to go to the definition of a library function outside of my current repository.
dumb-jump supports this through
.dumbjumpby letting me add additional paths:where the above would let me go to definition for locally installed pip packages in my system python.
However, often times library sources are in weird places. This differs user-to-user (e.g., b/c
$HOMEdoes) and is dependent on python configuration. For instance, for my recent poetry-based project, the python library sources would be found with:Obviously, this is all very user and system and language dependent, but if
dumb-jump.elwere to provide a hook to add include paths dynamically (i.e., after loading a.dumbjumpconfig), then I could add my own elisp logic which could dynamically generate system library paths based on the current buffer. E.g., if thelangis python then my hook could runpoetry run python -c 'import site; print(site.getsitepackages())'and add those to the:includeconfig.