I added support (to my version) for optional argument specific auto complete support

[mskacal]

If there is desire I can try to upload a PR with my changes

[wallstop]

Oh cool, tell me about it! I built a feature that did something where you could build like:

1. Type spawn (command is "spawn")
2. Hit tab
3. The system asks the spawn command for completion options and integrates them into the auto complete flow
4. Can continue with even more arguments, like spawn thing + even more completions

Does yours work something like that? If so, would love a PR.

[wallstop]

BTW, I have a few updates I want to push to this project:

1. Tech cleanup / refactoring
2. Quick-complete bar (similar to Flow Launcher)
3. The above

This project is just low priority for me currently.

[mskacal]

Yeah - you supply a list of lists as an additional optional variadic (or params for C# terms) - if it's -1 for max args I have a special case id you only supply one list to use it for every argument endlessly.

Resolution of the strings needs to be managed at the arg loading stage as these are just string representations but gives the ability to custom drive and command.

I hooked into the auto complete function and use space as separators.

I ran into some bugs within the system plugging all this in so there might be some nicer solutions to some of my fixes to just move forward in those cases.

If I can get a gif small enough to post here it would better demonstrate what I'm trying to explain.

[mskacal]

I also added a simple action delegate hook to easily allow external code to know when the system opens / closes such that they can enable / disable input maps that you probably don't want fighting with while you type in the console.

[wallstop]

Yeah - you supply a list of lists as an additional optional variadic (or params for C# terms) - if it's -1 for max args I have a special case id you only supply one list to use it for every argument endlessly.

Resolution of the strings needs to be managed at the arg loading stage as these are just string representations but gives the ability to custom drive and command.

I hooked into the auto complete function and use space as separators.

I ran into some bugs within the system plugging all this in so there might be some nicer solutions to some of my fixes to just move forward in those cases.

If I can get a gif small enough to post here it would better demonstrate what I'm trying to explain.

Ah cool, the functionality I'd be looking for in this kind of system is actually dynamic, context-aware auto-complete. That is, every command invocation queries the command to see what completions are available. This way you can do things like utilize the current state (level, thing you're looking at, player inventory, etc) to determine what is available.

If you link me your repo, and are ok with me poking through your code (just looking), I might be able to incorporate some of your great ideas into this! No need to put in the effort for a PR, although I do appreciate it. I also might be able to make my version compatible with your version so you can pull in upstream changes with minimal effort.

I have an implementation of the above locally, but it needs some work to be production ready.

[mskacal]

These are command specific - when you construct the command you supply the auto complete lists. But yeah will be easier to just show the code. Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Eli Pinkerton ***@***.***> Sent: Wednesday, January 14, 2026 7:39:02 PM To: wallstop/DxCommandTerminal ***@***.***> Cc: mskacal ***@***.***>; Author ***@***.***> Subject: Re: [wallstop/DxCommandTerminal] I added support (to my version) for optional argument specific auto complete support (Issue #31) [https://avatars.githubusercontent.com/u/1045249?s=20&v=4]wallstop left a comment (wallstop/DxCommandTerminal#31)<#31 (comment)> Yeah - you supply a list of lists as an additional optional variadic (or params for C# terms) - if it's -1 for max args I have a special case id you only supply one list to use it for every argument endlessly. Resolution of the strings needs to be managed at the arg loading stage as these are just string representations but gives the ability to custom drive and command. I hooked into the auto complete function and use space as separators. I ran into some bugs within the system plugging all this in so there might be some nicer solutions to some of my fixes to just move forward in those cases. If I can get a gif small enough to post here it would better demonstrate what I'm trying to explain. Ah cool, the functionality I'd be looking for in this kind of system is actually dynamic, context-aware auto-complete. That is, every command invocation queries the command to see what completions are available. This way you can do things like utilize the current state (level, thing you're looking at, player inventory, etc) to determine what is available. If you link me your repo, and are ok with me poking through your code (just looking), I might be able to incorporate some of your great ideas into this! I have an implementation of the above locally, but it needs some work to be production ready. — Reply to this email directly, view it on GitHub<#31 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAPUTEJ3TDUM66TLFXBKUKD4G4DVNAVCNFSM6AAAAACRWUJMOOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTONJSG43DOOJWGE>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[mskacal]

here is a gif example, here is single line example of how the command is built for the repeat infinite args case (I will look at making a PR later when I have more time). they can be argument specific (arg 1, arg 2, arg 3) etc as well - this one is just easiest to demo quickly.

[wallstop]

Thank you! No need to spend time on a PR, this is very similar to functionality that I want, which is specifically dynamic command arg. That is, I'd want a way to get both static (never changing, your version) and dynamic (changes every command) ways of this functionality, per-command. This kind of feature would require the dynamic aspect, for me. But I will take a peek at your implementation to try to make the version I come up with as compatible as possible, as well as ping this thread when it ships.

[mskacal]

extra code snippet context.

[mskacal]

Sounds like you are also looking into a function delegate hook that someone can custom right when it tries to talk to supply their own list of strings if I am understanding you correctly - that shouldn't be that much more effort to add either.

[wallstop]

Sounds like you are also looking into a function delegate hook that someone can custom right when it tries to talk to supply their own list of strings if I am understanding you correctly - that shouldn't be that much more effort to add either.

Exactly correct!