Open
Description
If you have multiple terminals within a group, only the first terminal in the group will have its name load. All subsequent terminals pick up the default process name.
Example LoadTerminal.json
{
"version": "packageJson.version",
"customGroup": [],
"groups": [
{
"name": "Active",
"description": "Main development group of terminals and commands",
"enabled": true,
"terminals": [
{
"name": "main",
"path": ".",
"cmd": [],
"num": 0
},
{
"name": "build",
"path": "./src",
"cmd": [
"build",
"yarn watch"
],
"num": 0
}
]
},
{
"name": "Background",
"description": "Background process terminals and commands",
"enabled": true,
"terminals": [
{
"name": "up",
"path": ".",
"cmd": [
"dev/up"
],
"num": 0
},
{
"name": "dashboard",
"path": ".",
"cmd": [
"minikube dashboard"
],
"num": 0
},
{
"name": "sw web",
"path": "./src/packages/web",
"cmd": [
"yarn swap"
],
"num": 0
}
]
}
]
}
Here's the actual terminal names and their initially-printed output:
active
group:main
(this is correct) terminal output:main cd . $ cd .
zsh
(this should bebuild
) terminal output:cd ./src build yarn watch $ cd ./src $ build $ yarn watch
background
group:up
(this is correct) terminal output:up cd . dev/up $ cd . $ dev/up
minikube
(this should bedashboard
) terminal output:cd . minikube dashboard $ cd . $ minikube dashboard
zsh
(this should besw web
) terminal output:cd ./src/packages/web yarn swap $ cd ./src/packages/web $ yarn swap
You'll notice that all terminals except the first per group are not actually setting the terminal name in the printed output.
Metadata
Assignees
Labels
No labels
Activity