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.

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

Not invoking extension when file opened by association #6

Open
RogerThiede opened this issue Dec 19, 2020 · 1 comment
Open

Not invoking extension when file opened by association #6

RogerThiede opened this issue Dec 19, 2020 · 1 comment

Comments

@RogerThiede
Copy link

The Binary-Plist extension is not used or properly activated when Visual Studio Code application is executed to open a specific file. Open Visual Studio Code via file association does not appear to invoke this extension when it should be invoked.

Works as expected:

  1. Execute Visual Studio Code
  2. Menu File->Open->Select binary .plist file
  3. Two tabs are opened, one in binary, and one in XML

Does not work as expected:

  1. Close Visual Studio Code if it is already running
  2. Associate .plist files with Visual Studio Code if not already done
  3. Double Click on a binary .plist file to open it
  4. Visual Studio Code starts with one tab opened, showing the file in binary form.
    Expected outcome: Two tabs are opened
@dnicolson
Copy link
Owner

dnicolson commented Dec 19, 2020

Opening a property list file using either method does not open an additional tab in most cases before clicking the "Do you want to open it anyway?". What you are describing could be possible if the XML tab was closed and Visual Studio Code was reopened with the binary file still open.

Can you provide a video of the problematic behavior?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants