From 6e9c2aec7e3be2dc49ea99916e4fc08f4d872ade Mon Sep 17 00:00:00 2001 From: Duncan <73707956+DuncanJoyLeeman@users.noreply.github.com> Date: Thu, 4 Sep 2025 13:38:33 +0200 Subject: [PATCH] Remove duplicate text about CWD workaround --- TerminalDocs/tutorials/new-tab-same-directory.md | 1 - 1 file changed, 1 deletion(-) diff --git a/TerminalDocs/tutorials/new-tab-same-directory.md b/TerminalDocs/tutorials/new-tab-same-directory.md index 3c5148ff..ac2b942a 100644 --- a/TerminalDocs/tutorials/new-tab-same-directory.md +++ b/TerminalDocs/tutorials/new-tab-same-directory.md @@ -14,7 +14,6 @@ Typically, the "new tab" and "split pane" actions will always open a new tab/pan Unfortunately, on Windows, it's tricky to determine what the current working directory ("CWD") for a process is. Even if we were able to look it up, not all applications actually set their CWD as they navigate. Notably, Windows PowerShell doesn't change its CWD as you `cd` around the file system! Duplicating the CWD of PowerShell automatically would almost always be wrong. -Fortunately, there's a workaround. Applications can emit a special escape sequence (specifically the "OSC 9;9" format) to manually tell the Terminal what the CWD should be. Fortunately, there's a workaround. Applications can emit a special escape sequence (specifically the "OSC 9;9" format) to manually tell the Terminal what the CWD should be. In this tutorial, you learn how to: