Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

macOS: opening documents by file path only is broken

See original GitHub issue

Prerequisites

Write a descriptive title.
Make sure you are able to repro it on the latest released version
Search the existing issues.
Refer to the FAQ.
Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce

The following is currently broken on macOS 12.6:

'hi' > t.txt
./t.txt  # !! Nothing happens.

Note that Invoke-Item ./t.txt works.

Expected behavior

./t.txt should open in the default text editor.

Actual behavior

Nothing happens.

Error details

No response

Environment data

PowerShell Core 7.3.0-preview.8 (also present in 7.2.6) on macOS 12.6 (M1)

Visuals

No response

Issue Analytics

State:
Created a year ago
Comments:7 (5 by maintainers)

Top GitHub Comments

1reaction

SteveL-MSFTcommented, Oct 4, 2022

Took a bit of time going through different versions of pwsh to find out where the regression was introduced and it was in 7.2-preview.6. It appears that the process is being started, but then immediately killed. I’ll have a fix.

1reaction

StevenBucher98commented, Oct 3, 2022

I’ll need to check it, but on Windows I always use Start-Process ./t.txt to open file in default program, I assumed that just ./t.txt would throw an equivalent of “file is not executable”

When you do ./t.txt it opens in notepad, also able to reproduce this on my mac, nothing happens.