Cannot launch new profile without explicitly specify startingDirectory #4898

Open
opened 2026-01-30 23:59:40 +00:00 by claunia · 0 comments
Owner

Originally created by @kiennq on GitHub (Nov 9, 2019).

Environment

Win32NT             10.0.19018.0 Microsoft Windows NT 10.0.19018.0
Windows Terminal (Preview)
Version: 0.6.3121.0

Steps to reproduce

Add a new custom profile, for example:

        {
            "guid": "{574d775e-4f2a-5b96-ac1e-a2962a402336}",
            "name": "Powershell Core",
            "commandline": "pwsh.exe",
            // without startingDirectory it will crash
            "acrylicOpacity": 1.0,
            "closeOnExit": true,
            "colorScheme": "One Half Dark",
            "cursorColor": "#FFFFFF",
            "cursorShape": "bar",
            "fontFace": "DelugiaCode NF",
            "fontSize": 10,
            "icon": "ms-appx:///ProfileIcons/{574e775e-4f2a-5b96-ac1e-a2962a402336}.png",
            "padding": "0, 0, 0, 0",
            "snapOnInput": true,
            "useAcrylic": true
        },

And try to launch it from the profiles dropdown

Expected behavior

Can launch new profile in new tab

Actual behavior

Cannot launch new profile

Originally created by @kiennq on GitHub (Nov 9, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Win32NT 10.0.19018.0 Microsoft Windows NT 10.0.19018.0 Windows Terminal (Preview) Version: 0.6.3121.0 ``` # Steps to reproduce Add a new custom profile, for example: ```jsonc { "guid": "{574d775e-4f2a-5b96-ac1e-a2962a402336}", "name": "Powershell Core", "commandline": "pwsh.exe", // without startingDirectory it will crash "acrylicOpacity": 1.0, "closeOnExit": true, "colorScheme": "One Half Dark", "cursorColor": "#FFFFFF", "cursorShape": "bar", "fontFace": "DelugiaCode NF", "fontSize": 10, "icon": "ms-appx:///ProfileIcons/{574e775e-4f2a-5b96-ac1e-a2962a402336}.png", "padding": "0, 0, 0, 0", "snapOnInput": true, "useAcrylic": true }, ``` And try to launch it from the profiles dropdown # Expected behavior Can launch new profile in new tab # Actual behavior Cannot launch new profile
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#4898