starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

/k argument ignored from 'commandline' setting #2123

New Issue
Closed
opened 2026-01-30 22:47:23 +00:00 by claunia · 2 comments
claunia commented 2026-01-30 22:47:23 +00:00
Owner
Copy Link

Originally created by @maciek-codes on GitHub (Jun 24, 2019).

Environment

Windows build number: 10.0.18362.207 
Windows Terminal version (if applicable): 0.2.21715.0

Steps to reproduce

I have setenv.bat file in S:\dir.

Add new command in profiles.json:
with "commandline": "cmd.exe **/k S:\\dir\\setenv.bat**", like this:

{
      "acrylicOpacity": 0.75,
      "closeOnExit": true,
      "colorScheme": "Campbell",
      "commandline": "cmd.exe **/k S:\\dir\\setenv.bat**",
      "cursorColor": "#FFFFFF",
      "cursorShape": "bar",
      "fontFace": "Consolas",
      "fontSize": 10,
      "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
      "historySize": 9001,
      "icon": "ms-appx:///ProfileIcons/{0caa0dad-35be-5f56-a8ff-afceeeaa6101}.png",
      "name": "cmd custom",
      "padding": "0, 0, 0, 0",
      "snapOnInput": true,
      "startingDirectory": "S:\\omaha\\src",
      "useAcrylic": true
    },

Expected behavior

I expect "cmd custom" to launch cmd.exe /k s:\dir\setenv.bat.

Actual behavior

setenv.bat is never launched.

Originally created by @maciek-codes on GitHub (Jun 24, 2019). <!-- 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. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.18362.207 Windows Terminal version (if applicable): 0.2.21715.0 ``` # Steps to reproduce I have setenv.bat file in S:\dir. Add new command in profiles.json: with `"commandline": "cmd.exe **/k S:\\dir\\setenv.bat**",` like this: ``` { "acrylicOpacity": 0.75, "closeOnExit": true, "colorScheme": "Campbell", "commandline": "cmd.exe **/k S:\\dir\\setenv.bat**", "cursorColor": "#FFFFFF", "cursorShape": "bar", "fontFace": "Consolas", "fontSize": 10, "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}", "historySize": 9001, "icon": "ms-appx:///ProfileIcons/{0caa0dad-35be-5f56-a8ff-afceeeaa6101}.png", "name": "cmd custom", "padding": "0, 0, 0, 0", "snapOnInput": true, "startingDirectory": "S:\\omaha\\src", "useAcrylic": true }, ``` # Expected behavior I expect "cmd custom" to launch cmd.exe /k s:\dir\setenv.bat. # Actual behavior setenv.bat is never launched.
claunia added the Needs-TriageNeeds-Tag-FixResolution-Answered labels 2026-01-30 22:47:23 +00:00
claunia commented 2026-01-30 22:47:24 +00:00
Author
Owner
Copy Link

@maciek-codes commented on GitHub (Jun 24, 2019):

I think my issue was not replacing the guid field.

@maciek-codes commented on GitHub (Jun 24, 2019): I think my issue was not replacing the guid field.
claunia commented 2026-01-30 22:47:24 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 24, 2019):

Cool. Resolved, then?

@DHowett-MSFT commented on GitHub (Jun 24, 2019): Cool. Resolved, then?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Tag-Fix Needs-Triage Resolution-Answered
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#2123
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?