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

Unable to set Command while running a cmd script #16829

New Issue
Closed
opened 2026-01-31 05:24:17 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 05:24:17 +00:00
Owner
Copy Link

Originally created by @jiveshwar on GitHub (Feb 20, 2022).

I want to open 1 of the windows with ssh login automatically, and hence I wrote a file abc.cmd with the following content, but it is giving errors:

wt.exe -p Bash -d "c:/test/folder1"; -p Bash -c "ssh test@192.168.0.10"; -p Bash -d "C:/Projects/test"; focus-tab -t 0

image

Also tried:
wt.exe -p Bash -d "c:/test/folder1"; -p Bash /c "ssh test@192.168.0.10"; -p Bash -d "C:/Projects/test"; focus-tab -t 0

but again got the similar error:
image

Is there any way I can set the commands as mentioned here:
image

Originally created by @jiveshwar on GitHub (Feb 20, 2022). I want to open 1 of the windows with ssh login automatically, and hence I wrote a file abc.cmd with the following content, but it is giving errors: `wt.exe -p Bash -d "c:/test/folder1"; -p Bash -c "ssh test@192.168.0.10"; -p Bash -d "C:/Projects/test"; focus-tab -t 0` ![image](https://user-images.githubusercontent.com/7592502/154863809-495ed993-9e2c-48d3-8965-afc46f3f6f63.png) Also tried: `wt.exe -p Bash -d "c:/test/folder1"; -p Bash /c "ssh test@192.168.0.10"; -p Bash -d "C:/Projects/test"; focus-tab -t 0` but again got the similar error: ![image](https://user-images.githubusercontent.com/7592502/154863856-6577f059-86e7-440b-8926-c36d74bcc65c.png) Is there any way I can set the commands as mentioned here: ![image](https://user-images.githubusercontent.com/7592502/154863942-f63dda5c-c552-4f5e-8837-4d37414262ef.png)
claunia commented 2026-01-31 05:24:20 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 22, 2022):

When you pass a commandline to a new-tab subcommand, it doesn't append that commandline to the profile's commandline, it replaces it. So when you do

new-tab -p Bash -c "ssh test@192.168.0.10"

You're telling wt:

  • open a new tab
  • use the "Bash" profile

But then our arg parser gets confused on the -c, because wt new-tab doesn't accept a -c arg itself.

The way you probably want do to this is

new-tab -p Bash -- {whatever the bash commandline is} -c ssh test@192.168.0.10

the -- will escape the remainder of the args to this new-tab command and treat the rest of the string as the new commandline.

Does that make sense?

@zadjii-msft commented on GitHub (Feb 22, 2022): When you pass a `commandline` to a `new-tab` subcommand, it doesn't _append_ that `commandline` to the profile's` commandline`, it _replaces_ it. So when you do ``` new-tab -p Bash -c "ssh test@192.168.0.10" ``` You're telling `wt`: * open a new tab * use the "Bash" profile But then our arg parser gets confused on the `-c`, because `wt new-tab` doesn't accept a `-c` arg itself. The way you probably want do to this is ``` new-tab -p Bash -- {whatever the bash commandline is} -c ssh test@192.168.0.10 ``` the `--` will escape the remainder of the args to this `new-tab` command and treat the rest of the string as the new `commandline`. Does that make sense?
claunia commented 2026-01-31 05:24:20 +00:00
Author
Owner
Copy Link

@jiveshwar commented on GitHub (Feb 22, 2022):

I think the syntax is something else. This is not working
wt.exe -p Bash -- -c ssh test@192.168.0.10
AND
wt.exe -p Bash -- ssh test@192.168.0.10
AND
wt.exe new-tab -p Bash -- -c ssh test@192.168.0.10
AND
wt.exe new-tab -p Bash -- ssh test@192.168.0.10

all are giving errors like:
image

@jiveshwar commented on GitHub (Feb 22, 2022): I think the syntax is something else. This is not working `wt.exe -p Bash -- -c ssh test@192.168.0.10` AND `wt.exe -p Bash -- ssh test@192.168.0.10` AND `wt.exe new-tab -p Bash -- -c ssh test@192.168.0.10` AND `wt.exe new-tab -p Bash -- ssh test@192.168.0.10` all are giving errors like: ![image](https://user-images.githubusercontent.com/7592502/155170919-47143687-0ca2-4241-89f8-a62d3f34c57b.png)
claunia commented 2026-01-31 05:24:21 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 22, 2022):

That's exactly what I'd expect to happen there. You need to make sure to add the Bash profile's commandline to the start. What's the commandline of your Bash profile? Something like c:\path\to\bash.exe --some -args? Then your command would need to be

new-tab -p Bash -- c:\path\to\bash.exe --some -args -c ssh test@192.168.0.10
@zadjii-msft commented on GitHub (Feb 22, 2022): That's exactly what I'd expect to happen there. You need to make sure to add the Bash profile's `commandline` to the start. What's the commandline of your Bash profile? Something like `c:\path\to\bash.exe --some -args`? Then your command would need to be ``` new-tab -p Bash -- c:\path\to\bash.exe --some -args -c ssh test@192.168.0.10 ```
claunia commented 2026-01-31 05:24:21 +00:00
Author
Owner
Copy Link

@237dmitry commented on GitHub (Feb 23, 2022):

Why explicitly use the --profile parameter if the profile picks up the command anyway? For example I set micro in profiles, when I launch this editor from script the terminal opens this editor according to its profile settings (font, cursor, tab color):

param (
    [Parameter(Mandatory)]
    [string] $file
)

$Env:MICRO_TRUECOLOR = 1

$file = Get-Item $file
wt --window 0 new-tab --startingDirectory $file.Directory micro $file.Name
@237dmitry commented on GitHub (Feb 23, 2022): Why explicitly use the `--profile` parameter if the profile picks up the command anyway? For example I set `micro` in profiles, when I launch this editor from script the terminal opens this editor according to its profile settings (font, cursor, tab color): ```powershell param ( [Parameter(Mandatory)] [string] $file ) $Env:MICRO_TRUECOLOR = 1 $file = Get-Item $file wt --window 0 new-tab --startingDirectory $file.Directory micro $file.Name ```
claunia commented 2026-01-31 05:24:21 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 23, 2022):

A Profile is a lot more than just a commandline, perhaps OP want's to make sure to use the colorscheme, font, etc. from their "Bash" profile rather than their default settings.

@zadjii-msft commented on GitHub (Feb 23, 2022): A Profile is a lot more than just a commandline, perhaps OP want's to make sure to use the colorscheme, font, etc. from their "Bash" profile rather than their default settings.
claunia commented 2026-01-31 05:24:22 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 27, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Feb 27, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
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 Area-Commandline Issue-Question Needs-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity 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#16829
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?