You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OSC 7 is an escape sequence to notify the terminal emulator of the program's current working directory. There is no formal spec for this. Efforts were made in freedesktop.org's terminal-wg, but these seem stalled.
However, OSC 7 is widely supported.
Here's macOS Sequoia's description of it:
Here's a summary of findings I made of wider adoption (trying to justify why an existing application should print OSC 7):
There also exist the related OSC 1337 proprietary to iTerm2, and OSC 633 proprietary to VSCode, and OSC 9;9 supported on Windows by ConEmu and Windows Terminal.
Not sure if it makes sense to support OSC 1337 and OSC 633, maybe it does make sense to support OSC 9;9 too?
I started work on a PR for just OSC 7, but it seems like to write unit tests charmbracelet/x/ansi also needs to support this, so I'll create this ticket first for referencing.
The text was updated successfully, but these errors were encountered:
OSC 7
is an escape sequence to notify the terminal emulator of the program's current working directory. There is no formal spec for this. Efforts were made in freedesktop.org's terminal-wg, but these seem stalled.However,
OSC 7
is widely supported.Here's macOS Sequoia's description of it:
Here's a summary of findings I made of wider adoption (trying to justify why an existing application should print
OSC 7
):There also exist the related
OSC 1337
proprietary to iTerm2, andOSC 633
proprietary to VSCode, andOSC 9;9
supported on Windows by ConEmu and Windows Terminal.Not sure if it makes sense to support
OSC 1337
andOSC 633
, maybe it does make sense to supportOSC 9;9
too?I started work on a PR for just
OSC 7
, but it seems like to write unit testscharmbracelet/x/ansi
also needs to support this, so I'll create this ticket first for referencing.The text was updated successfully, but these errors were encountered: