COMMAND$ and wildcards on files
#10
(12-30-2022, 04:21 PM)Spriggsy Wrote: I'm confused. Why aren't you using COMMAND$(n)? You can iterate through arguments with that. No need for a separate call to the WinAPI.

In the first post it seems to be that the original poster doesn't want that behavior, would rather have the asterisks:

Quote:Is it possible to get this argument just as test*.* instead of many arguments? Especiallly when combing this with recursing, this behaviour makes it difficult to handle it so for a user it feels logically.

Yes it could be confusing.
Reply


Messages In This Thread
COMMAND$ and wildcards on files - by zaadstra - 12-24-2022, 05:12 PM
RE: COMMAND$ and wildcards on files - by SMcNeill - 12-24-2022, 07:35 PM
RE: COMMAND$ and wildcards on files - by zaadstra - 12-25-2022, 12:33 AM
RE: COMMAND$ and wildcards on files - by SMcNeill - 12-25-2022, 12:48 AM
RE: COMMAND$ and wildcards on files - by mdijkens - 12-25-2022, 08:10 AM
RE: COMMAND$ and wildcards on files - by zaadstra - 12-25-2022, 04:23 PM
RE: COMMAND$ and wildcards on files - by zaadstra - 12-29-2022, 05:58 PM
RE: COMMAND$ and wildcards on files - by mdijkens - 12-30-2022, 01:01 PM
RE: COMMAND$ and wildcards on files - by mnrvovrfc - 12-30-2022, 04:34 PM
RE: COMMAND$ and wildcards on files - by mdijkens - 12-30-2022, 06:11 PM
RE: COMMAND$ and wildcards on files - by zaadstra - 01-17-2023, 10:12 PM
RE: COMMAND$ and wildcards on files - by zaadstra - 01-19-2023, 05:25 PM
RE: COMMAND$ and wildcards on files - by mdijkens - 01-19-2023, 05:59 PM
RE: COMMAND$ and wildcards on files - by zaadstra - 01-19-2023, 07:31 PM



Users browsing this thread: 6 Guest(s)