Aaron Matthis

Either way will be breaking, so how about doing a fair cleanup (and bumping the major version)? Aka condensing the code we need and adding an explicit interface via methods

While it's true that `CONFIG` seems to be a good place, having `interactive_matcher` untyped doesn't seem so. Tab completion doesn't help if you can't infer which type you need to...

Ran into the same ^^ Since the Artifact system arrived, this might be even easier. :D I might eventually give it a shot if I find time 😅

I guess you want to keep Julia LTS compat, thus, even if I can make an artifacts solution, I have now clue how to backport that for pre 1.3 🤔

Btw, when searching, where to put that code to, I found that part: ```julia @static if VERSION < v"0.7-" [...] ``` You might want to consider dropping all that pre...

Finally after just too much time for that amount of code 😄 https://github.com/tkf/InteractiveCodeSearch.jl/pull/10 Though, on julia pre 1.3 the package is somewhat unnecessary (but shouldn't fail is its not used)......

> If I understand it right, for this method, the only valid option left in `args...` is `alg`; I think the right dispatch should be > > ```julia > function...

I guess it's nothing about the platform, but that juliaup itself didn't update to 1.8.1 for me at least: running right now: ``` C:\Users\Aaron>juliaup list Channel Version ------------------------------------ [...] 1.7~x64...

does the `DiGraph(.)` copy? I.e. can I use `transitiveclosure!` ?

Well, I actually envisioned it as a reference (key) whose only purpose is to be selected in place of a keyboard press (i.e. referring to other keybindings). So nesting (=referring...