summaryrefslogtreecommitdiff
path: root/modules/prog-python.el
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-05-15 02:21:57 -0500
committerCraig Jennings <c@cjennings.net>2026-05-15 02:21:57 -0500
commitff55d4f95348335f7fa15f6bf4e2398cb72bb3c6 (patch)
tree0f25df4acf183b47e6f02d5651d542ef148be011 /modules/prog-python.el
parent97961ce1ede990807d71b5d462bf44cc006b46d4 (diff)
downloaddotemacs-ff55d4f95348335f7fa15f6bf4e2398cb72bb3c6.tar.gz
dotemacs-ff55d4f95348335f7fa15f6bf4e2398cb72bb3c6.zip
fix(ai-vterm): autoload cj/toggle-gptel to silence cross-module warning
make compile warned that cj/toggle-gptel is not known to be defined when ai-vterm.el is byte-compiled. The M-F9 binding still worked during normal startup because init.el loads ai-config.el after ai-vterm.el, but the dependency was implicit -- byte-compile saw the function symbol unresolved, and loading ai-vterm.el in isolation left M-F9 bound to an undefined function. Declare cj/toggle-gptel as an interactive autoload pointing at ai-config. This silences the warning, keeps ai-vterm.el free of a load-time (require 'ai-config), and makes the load-order contract explicit: the binding works as long as ai-config eventually loads. Test asserts that requiring ai-vterm in isolation leaves cj/toggle-gptel fboundp as an autoload sigil (not a real function). A regression that adds (require 'ai-config) at the top of ai-vterm.el would flip this, and a regression that drops the autoload form would leave fboundp nil.
Diffstat (limited to 'modules/prog-python.el')
0 files changed, 0 insertions, 0 deletions