Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Unexpected behavior in command execution when two files have the same basename. #2095

Copy link
Copy link
Closed
Closed
Unexpected behavior in command execution when two files have the same basename.#2095
Copy link
Assignees
SteveL-MSFT
Labels
Committee-ReviewedPS-Committee has reviewed this and made a decisionPS-Committee has reviewed this and made a decisionIssue-BugIssue has been identified as a bug in the productIssue has been identified as a bug in the productIssue-Discussionthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifResolution-FixedThe issue is fixed.The issue is fixed.WG-Enginecore PowerShell engine, interpreter, and runtimecore PowerShell engine, interpreter, and runtime
Milestone
6.0.0-GA
@nocentino

Description

@nocentino
nocentino
opened on Aug 27, 2016
Issue body actions

Steps to reproduce

Create two files

  1. Simple shell script, name it loop and mark it executable
  2. Simple powershell script, name it loop.ps1

Expected behavior

Typing ./loop should launch the program loop

Actual behavior

When you type ./loop you would expect loop (the first file) to execute. It does not, in fact loop.ps1 executes.

Environment data

Name                           Value                                                                         
----                           -----                                                                         
PSVersion                      5.1.10032.0                                                                   
PSEdition                      Linux                                                                         
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}                                                       
BuildVersion                   3.0.0.0                                                                       
GitCommitId                    v0.6.0                                                                        
CLRVersion                                                                                                   
WSManStackVersion              1.0                                                                           
PSRemotingProtocolVersion      2.3                                                                           
SerializationVersion           1.1.0.1
Reactions are currently unavailable

Metadata

Metadata

Assignees

Labels

Committee-ReviewedPS-Committee has reviewed this and made a decisionPS-Committee has reviewed this and made a decisionIssue-BugIssue has been identified as a bug in the productIssue has been identified as a bug in the productIssue-Discussionthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifResolution-FixedThe issue is fixed.The issue is fixed.WG-Enginecore PowerShell engine, interpreter, and runtimecore PowerShell engine, interpreter, and runtime

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions
    Morty Proxy This is a proxified and sanitized view of the page, visit original site.