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

Please provide setting option add the start-up Commands for the Machines #10848

New Issue
Closed
opened 2026-01-31 02:31:51 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 02:31:51 +00:00
Owner
Copy Link

Originally created by @jiveshwar on GitHub (Oct 1, 2020).

Please add the option to add some startUpCommands in each machine, such as:

{
	"guid": "{95ca431a-2vw37-1fb3-1hcf-sjd84745465}",
	"name": "Kali-Linux",
	"hidden": false,
	"startUpCommands": "ssh myServer;cd /var/logs/test;"
},
{
	"guid": "{95ca431a-2vw37-1fb3-1hcf-sjd84745466}",
	"name": "Kali-Linux-2",
	"hidden": false,
	"startUpCommands": "cd /var/git-repo;git pull;"
},
Originally created by @jiveshwar on GitHub (Oct 1, 2020). Please add the option to add some **startUpCommands** in each machine, such as: { "guid": "{95ca431a-2vw37-1fb3-1hcf-sjd84745465}", "name": "Kali-Linux", "hidden": false, "startUpCommands": "ssh myServer;cd /var/logs/test;" }, { "guid": "{95ca431a-2vw37-1fb3-1hcf-sjd84745466}", "name": "Kali-Linux-2", "hidden": false, "startUpCommands": "cd /var/git-repo;git pull;" },
claunia added the Issue-QuestionArea-SettingsResolution-AnsweredProduct-Terminal labels 2026-01-31 02:31:52 +00:00
claunia commented 2026-01-31 02:31:52 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 1, 2020):

You mean like maybe, the commandline property?

Ah okay, I see what you're trying to do. You're trying to ssh directly to a specific directory on the remote machine. That's unfortunately really hard to do (for whatever reason). This thread might have some suggestions for you: https://github.com/MicrosoftDocs/terminal/issues/25#issuecomment-631515603

@zadjii-msft commented on GitHub (Oct 1, 2020): ~~You mean like maybe, the [`commandline` property](https://docs.microsoft.com/en-us/windows/terminal/customize-settings/profile-settings#command-line)?~~ Ah okay, I see what you're trying to do. You're trying to ssh directly to a specific directory on the remote machine. That's unfortunately really hard to do (for whatever reason). This thread might have some suggestions for you: https://github.com/MicrosoftDocs/terminal/issues/25#issuecomment-631515603
claunia commented 2026-01-31 02:31:53 +00:00
Author
Owner
Copy Link

@jiveshwar commented on GitHub (Oct 1, 2020):

You mean like maybe, the commandline property?

Ah okay, I see what you're trying to do. You're trying to ssh directly to a specific directory on the remote machine. That's unfortunately really hard to do (for whatever reason). This thread might have some suggestions for you: MicrosoftDocs/terminal#25 (comment)

Thanks for the reply. I actually want something similar to shell script to work in this field value. I have updated my question for a better visibility.

@jiveshwar commented on GitHub (Oct 1, 2020): > ~You mean like maybe, the [`commandline` property](https://docs.microsoft.com/en-us/windows/terminal/customize-settings/profile-settings#command-line)?~ > > Ah okay, I see what you're trying to do. You're trying to ssh directly to a specific directory on the remote machine. That's unfortunately really hard to do (for whatever reason). This thread might have some suggestions for you: [MicrosoftDocs/terminal#25 (comment)](https://github.com/MicrosoftDocs/terminal/issues/25#issuecomment-631515603) Thanks for the reply. I actually want something similar to shell script to work in this field value. I have updated my question for a better visibility.
claunia commented 2026-01-31 02:31:53 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 1, 2020):

The explanation is the same for running a shell script as it is for changing to a directory. https://github.com/MicrosoftDocs/terminal/issues/25#issuecomment-631515603 is going to be your best bet.

Terminal isn't intending on supporting "startup commands" -- they're fragile and prone to failure, because they are pretty much always implemented by pretending that the user typed that command when they launch a new tab. There's far better ways to run commands on startup: passing them as arguments, writing script wrappers, putting startup actions in your shell profile (.bashrc, profile.ps1, etc.), etc.

@DHowett commented on GitHub (Oct 1, 2020): The explanation is the same for running a shell script as it is for changing to a directory. https://github.com/MicrosoftDocs/terminal/issues/25#issuecomment-631515603 is going to be your best bet. Terminal isn't intending on supporting "startup commands" -- they're fragile and prone to failure, because they are pretty much always implemented by pretending that the user typed that command when they launch a new tab. There's far better ways to run commands on startup: passing them as arguments, writing script wrappers, putting startup actions in your shell profile (`.bashrc`, `profile.ps1`, etc.), etc.
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-Settings Issue-Question Product-Terminal 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#10848
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?