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

Degradation with multiple tabs and using nvm #19005

New Issue
Closed
opened 2026-01-31 06:30:53 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 06:30:53 +00:00
Owner
Copy Link

Originally created by @Filyus on GitHub (Dec 2, 2022).

Windows Terminal version

1.15.2874.0

Windows build number

10.0.19045.2251

Other Software

Steps to reproduce

  1. Download and run nvm-setup.exe from nvm-windows releases page
  2. Insall Node.js 16.17.0 via nvm-windows:
    nvm install 16.17.0
  3. Install NestJS:
    npm i -g @nestjs/cli
  4. Create projects:
cd /d C:\

nest new project-1
# select `npm` and press `Enter`

nest new project-2
# select `npm` and press `Enter`

nest new project-3
# select `npm` and press `Enter`
  1. Create a start.bat file to run 3 tabs with the created projects:
wt new-tab --title "Project 1" --suppressApplicationTitle -d "C:/project-1/" "%APPDATA%\nvm\v16.17.0\npm.cmd run start:dev"; new-tab --title "Project 2" --suppressApplicationTitle -d "C:/project-2/" "%APPDATA%\nvm\v16.17.0\npm.cmd run start:dev"; new-tab --title "Project 3" --suppressApplicationTitle -d "C:/project-3/" "%APPDATA%\nvm\v16.17.0\npm.cmd run start:dev"; focus-tab -t 0
  1. Set Startup > New instance behavior to Create a new window
  2. Close all the Windows Terminal instances
  3. Run start.bat

Expected Behavior

  1. Only one window is opened
  2. 3 tabs with correct titles is opened (specified in bat-file)
  3. The titles do not change over time
  4. Tabs order is same as in bat-file
  5. Focus changed to the first tab
  6. Every project in every tab is immediately started
  7. Closing Windows Terminal stops node instances
  8. Working with npm run dev inside of bat-file

Actual Behavior

  1. 3 windows instead of 1 is started (can be fixed by Startup > New instance behavior > Attach to the most recently used window setting, but this is dirty!)
  2. Titles is not always correct (some randomness here)
  3. Titles change to "Default" over time
  4. Tabs order is random
  5. Focus to the first tab is not changed, a last tab is focused
  6. Project in the first opened tab is not started while you not switch to that tab manualy
  7. Closing Windows Terminal don't stops node instances
  8. Full path of npm must be specified because of symbol link from C:\Program Files\nodejs to %APPDATA%\nvm\v16.17.0\ directory
Originally created by @Filyus on GitHub (Dec 2, 2022). ### Windows Terminal version 1.15.2874.0 ### Windows build number 10.0.19045.2251 ### Other Software - [nvm-windows](https://github.com/coreybutler/nvm-windows) 1.1.10 - [Node.js](https://nodejs.org/en/) 16.17.0 installed via `nvm-windows` - [NestJS](https://nestjs.com/) 9.0.0 ### Steps to reproduce 1. Download and run `nvm-setup.exe` from [nvm-windows releases page](https://github.com/coreybutler/nvm-windows/releases) 2. Insall `Node.js 16.17.0` via `nvm-windows`:\ `nvm install 16.17.0` 3. Install `NestJS`: `npm i -g @nestjs/cli` 4. Create projects: ```shell cd /d C:\ nest new project-1 # select `npm` and press `Enter` nest new project-2 # select `npm` and press `Enter` nest new project-3 # select `npm` and press `Enter` ``` 5. Create a `start.bat` file to run 3 tabs with the created projects: ```bat wt new-tab --title "Project 1" --suppressApplicationTitle -d "C:/project-1/" "%APPDATA%\nvm\v16.17.0\npm.cmd run start:dev"; new-tab --title "Project 2" --suppressApplicationTitle -d "C:/project-2/" "%APPDATA%\nvm\v16.17.0\npm.cmd run start:dev"; new-tab --title "Project 3" --suppressApplicationTitle -d "C:/project-3/" "%APPDATA%\nvm\v16.17.0\npm.cmd run start:dev"; focus-tab -t 0 ``` 6. Set `Startup` > `New instance behavior` to `Create a new window` 7. Close all the `Windows Terminal` instances 8. Run `start.bat` ### Expected Behavior 1. Only one window is opened 2. 3 tabs with correct titles is opened (specified in bat-file) 3. The titles do not change over time 4. Tabs order is same as in bat-file 5. Focus changed to the first tab 6. Every project in every tab is immediately started 7. Closing Windows Terminal stops node instances 8. Working with `npm run dev` inside of bat-file ### Actual Behavior 1. 3 windows instead of 1 is started (can be fixed by `Startup` > `New instance behavior` > `Attach to the most recently used window` setting, but this is dirty!) 2. Titles is not always correct (some randomness here) 3. Titles change to "Default" over time 4. Tabs order is random 5. Focus to the first tab is not changed, a last tab is focused 6. Project in the first opened tab is not started while you not switch to that tab manualy 7. Closing Windows Terminal don't stops node instances 8. Full path of `npm` must be specified because of symbol link from `C:\Program Files\nodejs` to `%APPDATA%\nvm\v16.17.0\` directory
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:30:54 +00:00
claunia commented 2026-01-31 06:30:55 +00:00
Author
Owner
Copy Link

@Filyus commented on GitHub (Dec 20, 2022):

Related issue: https://github.com/microsoft/terminal/issues/9628

This successfully runs with cmd /k and with disabled Run this profile as Administrator option or with a created shotcut to the bat-file with an enabled property Advanced > Run as administrator.

wt -w MyProject new-tab --title "Project 1" --suppressApplicationTitle -d "C:/project-1/" cmd /k "npm run start:dev"; new-tab --title "Project 2" --suppressApplicationTitle -d "C:/project-2/" cmd /k "npm run start:dev"; new-tab --title "Project 3" --suppressApplicationTitle -d "C:/project-3/" cmd /k "npm run start:dev"; focus-tab -t 0
@Filyus commented on GitHub (Dec 20, 2022): Related issue: https://github.com/microsoft/terminal/issues/9628 This successfully runs with `cmd /k` and with disabled `Run this profile as Administrator` option or with a created shotcut to the bat-file with an enabled property `Advanced > Run as administrator`. ```shell wt -w MyProject new-tab --title "Project 1" --suppressApplicationTitle -d "C:/project-1/" cmd /k "npm run start:dev"; new-tab --title "Project 2" --suppressApplicationTitle -d "C:/project-2/" cmd /k "npm run start:dev"; new-tab --title "Project 3" --suppressApplicationTitle -d "C:/project-3/" cmd /k "npm run start:dev"; focus-tab -t 0 ```
claunia commented 2026-01-31 06:30:55 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jan 25, 2023):

Commandline args actually use the same code as startupActions. So we're going to mark this as a /dup of #14442. Thanks.

@carlos-zamora commented on GitHub (Jan 25, 2023): Commandline args actually use the same code as startupActions. So we're going to mark this as a /dup of #14442. Thanks.
claunia commented 2026-01-31 06:30:55 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 25, 2023):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jan 25, 2023): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
claunia commented 2026-01-31 06:30:55 +00:00
Author
Owner
Copy Link

@Filyus commented on GitHub (Jan 26, 2023):

This is not a duplicate. Here are 8 (!) issues that are only hides by changing the administrator stuff. This doesn't mean that these issues don't need to be fixed. Please don't lose sight of them.

For example, my tab titles change by themselves to "Command Promt" now (like in an issue number 3 in the list above).

@Filyus commented on GitHub (Jan 26, 2023): This is not a duplicate. Here are 8 (!) issues that are only hides by changing the administrator stuff. This doesn't mean that these issues don't need to be fixed. Please don't lose sight of them. For example, my tab titles change by themselves to "Command Promt" now (like in an issue number 3 in the list above).
claunia commented 2026-01-31 06:30:56 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 26, 2023):

(For what it's worth, we do try to avoid having "blanket bugs" - it makes tracking them surprisingly difficult. After all: they do not represent indivisible units of work...) I would reckon that at least six of them are already tracked in the approx. 1500 open issues, it's just that we have not gone back and looked up all of those duplicates.

Sorry for the inconvenience, and thank you for following up :)

@DHowett commented on GitHub (Jan 26, 2023): (For what it's worth, we do try to avoid having "blanket bugs" - it makes tracking them surprisingly difficult. After all: they do not represent indivisible units of work...) I would reckon that at least six of them are already tracked in the approx. 1500 open issues, it's just that we have not gone back and looked up all of those duplicates. Sorry for the inconvenience, and thank you for following up :)
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 Issue-Bug Resolution-Duplicate
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#19005
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?