Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update new-tab-same-directory.md to mention OSC 9;9 #779

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update new-tab-same-directory.md to mention OSC 9;9 #779

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion TerminalDocs/tutorials/new-tab-same-directory.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ 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 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:

Expand Down