How to determine if command is available

[sebthom]

Does clink provide a convenient Lua function to determine if a command is available, i.e. is on PATH?

Something like e.g. Clink.isCommandPresent("gcc").

[chrisant996]

No, but it's easy to do it yourself.

Loop over ipairs(string.explode(os.getenv("path"), ";")) and use os.isfile(path.join(dir_from_path, name_to_find). If the input name_to_find doesn't include an extension, then you'll want to also loop over either a list of predefined extensions or ipairs(string.explode(os.getenv("pathext"), ";")) and try os.isfile(name_to_find .. each_ext_from_list).

[sebthom]

Yes I meant the where command. I am switching a lot between windows/linux.

I think what would help is if clink displays a warning if two argmatchers try to register for the same command.

[chrisant996]

I think what would help is if clink displays a warning if two argmatchers try to register for the same command.

That is explicitly a feature, and enables enhancing and merging argmatchers. It's documented in clink.argmatcher().

I can make the clink-diagnostics command list the sources that have contributed to a merged argmatcher.

But a warning isn't feasible. In fact, it used to display a warning. That's what led to user reports alerting me that v1.x had broken the merging feature that had existed since cb07751 in v0.4. That led me to add merging to v1.3.11 and fix some bugs in the v0.4.9 implementation and add some minor enhancements (Martin hadn't gotten around to adding it to the v1.x rewrite yet, or maybe had decided to cut it, I don't know).

Merging has varying degrees of success, depending on what's being done. But for at least a while, Cmder was even making use of that IIRC. I've also seen various other instances of intentionally using merging to extend existing argmatchers. There is only so much that can be done for merging, though, as it can inherently get very complicated very quickly.

[chrisant996]

I forgot mention that for clink-diagnostics to list argmatchers an argument of 2 or greater is needed, e.g. Alt-2,Ctrl-X,Ctrl-Z.

Btw, "merging" is a little ambiguous. The following is just defining an argmatcher. But it uses an approach that is indistinguishable from merging. So clink-diagnostics will report this as being a merged argmatcher, even though that wouldn't have been the intent. Not a problem, but it could look weird/confusing if any scripts use that kind of approach.

my_foo_argmatcher.lua

clink.argmatcher("foo"):addflags("--the", "--flags", "--for", "--foo", "--command")
clink.argmatcher("foo"):addarg({
    "some", "values", "for", "argument", "position", "ONE"
}) -- This is to illustrate that checking for immediately adjacent source lines isn't viable for detecting this sort of case.
clink.argmatcher("foo"):addarg("and", "values", "for", "argument", "position", "TWO")

How merging gets reported by the clink-diagnostics command

...
argmatchers:
  ...
  foo                            :  c:\wbin\clink\my_foo_argmatcher.lua:1
    merged with                  :  c:\wbin\clink\my_foo_argmatcher.lua:2
    merged with                  :  c:\wbin\clink\my_foo_argmatcher.lua:5
  ...
...

[sebthom]

I am confused about how to invoke the clink-diagnostics command pressing ctrl+x or ctrl+z as listed in the documentation does nothing.

Is it possible to determine from code if an argmatcher is already registered for a given command? Since I created completions for openssl and curl in my repo similar ones now also exist in vladimir-kotikov/clink-completions so I would like to register my completion defensive, meaning only to register them as long as no binding is there already.

[chrisant996]

I am confused about how to invoke the clink-diagnostics command pressing ctrl+x or ctrl+z as listed in the documentation does nothing.

Press Alt-2 then Ctrl-X then Ctrl-Z. Unless you've bound the sequence to something else. And assuming you aren't using vi mode.

Is it possible to determine from code if an argmatcher is already registered for a given command? Since I created completions for openssl and curl in my repo similar ones now also exist in vladimir-kotikov/clink-completions so I would like to register my completion defensive, meaning only to register them as long as no binding is there already.

clink.getargmatcher()