Skip to content

Is it worth writing up an RFC on adding new escape characters? #2751

@rkeithhill

Description

@rkeithhill

Given the inherent breaking changes between Windows PowerShell 5.x and PowerShell Core, especially when running on Linux and macOS, can we consider adding a few new escape characters?

With the addition of ANSI esc sequences to the Windows console host, and existence of the same on terminals in Linux and macOS, I would like to have the following esc chars added:

`e - ASCII escape char 0x1b
`u - specify Unicode character `u<hex-digit>+ e.g. `u2261
`_ - more "visible/obvious" line continuation

OK, so that last one is a stretch but there seems to be a few problems with line continuation in PowerShell - hard to see / trailing whitespace. Maybe PowerShell Core presents an opportunity to tweak line continuation a little??

If the PowerShell Committee is willing to entertain this idea, is it worth writing up as an RFC?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Committee-ReviewedPS-Committee has reviewed this and made a decisionIssue-Enhancementthe issue is more of a feature request than a bugResolution-FixedThe issue is fixed.Up-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsWG-Languageparser, language semantics

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions