Skip to content

Extensions: Be able to differentiate binary files that are opened as plaintext files from "real" plaintext files #131076

@damien-urruty-sonarsource

Description

When users open binary files, they are prompted with this message : "The file is not displayed in the editor because it is either binary or uses an unsupported text encoding. Do you want to open it anyway ?". If the user chooses to open it anyway, the binary file is then opened as a plaintext file.

Plain text files is something we are interested in in our extension, but we are not interested in binary files.

The problem today is that from an extension point of view, both (forced open) binary files and true plain text files will be seen as plaintext, and we have no easy way to differentiate between them.

I think it would make more sense to have a binary file type and not rely on the plaintext type in this situation.

Metadata

Metadata

Assignees

Labels

feature-requestRequest for new features or functionalityinsiders-releasedPatch has been released in VS Code Insidersverification-neededVerification of issue is requestedverifiedVerification succeededworkbench-editorsManaging of editor widgets in workbench window

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions