Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
S
specifications
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 20
    • Issues 20
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 4
    • Merge Requests 4
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Packages
    • Packages
    • Container Registry
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • terminal-wg
  • specifications
  • Issues
  • #20

Closed
Open
Opened Nov 01, 2019 by Christian Duerr@chrisduerr
  • Report abuse
  • New issue
Report abuse New issue

Specify OSC 7 behavior

The OSC 7 escape is already used by many terminal emulators (including for example VTE and Terminal.app), to inform the terminal about the currently active working directory. One of its use cases is that it allows reliably opening new terminals in the current working directory, assuming that client support is present.

An implementation for Alacritty was proposed in https://github.com/jwilm/alacritty/pull/2937, however to my knowledge there is no documentation on the behavior of this escape.

Creating a more formal standard describing the behavior in a specification on this project rather than using existing implementations would both help with consistency across implementations and might also be a great example of the terminal-wg's goals.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: terminal-wg/specifications#20