Intelligent Terminal version
0.1.1531.0
Windows build number
10.0.26200.0
Other Software
powershell 7.6.2
Steps to reproduce
Ask "How do I use X", where X is an existing PowerShell script on the path. an exiting program, or a non-exitent command.
Expected Behavior
For non-existent commands at the very least it should indicate that no such command can be found. Better: it should stry to co spelling correction using the commands that are on the path.
Actual Behavior
Ignores PowerShell scripts and presumably programs, etc, available on the path. It seems to know about some apps, for these it supplies pertinent information. However, for local apps, for example my PowerShell scripts, it doesn't even check whether the command is available. It delivers the same advice (use help or get-command) irrespective of whether the command exists or not. At the minimum it should say there is no such command. Better it should check whether it i9s a misspelling of a command on the path.
Intelligent Terminal version
0.1.1531.0
Windows build number
10.0.26200.0
Other Software
powershell 7.6.2
Steps to reproduce
Ask "How do I use X", where X is an existing PowerShell script on the path. an exiting program, or a non-exitent command.
Expected Behavior
For non-existent commands at the very least it should indicate that no such command can be found. Better: it should stry to co spelling correction using the commands that are on the path.
Actual Behavior
Ignores PowerShell scripts and presumably programs, etc, available on the path. It seems to know about some apps, for these it supplies pertinent information. However, for local apps, for example my PowerShell scripts, it doesn't even check whether the command is available. It delivers the same advice (use help or get-command) irrespective of whether the command exists or not. At the minimum it should say there is no such command. Better it should check whether it i9s a misspelling of a command on the path.