RUNME NOTEBOOKS shows wrong markdown files

[rubensa]

It should respect the workbench.editorAssociations setting to filter out those extensions not associated with runme.

I just want the default editor to be used for *.md files but runme editor por *.runme files so I set:

        "workbench.editorAssociations": {
          // Use default editor for markdown files (do not use runme editor)
          "*.md": "default",
          // Use runme editor for extended runable markdown files
          "*.runme": "runme"
        },

The files are opened with the right editor but the RUNME NOTEBOOKS shows .md (but it should show .runme files instead).

[sourishkrout]

Hi @rubensa. Thanks for reporting the issue. While default works locally for me. I believe the out-of-the-box settings is below, not default:

  "workbench.editorAssociations": {
    "*.md": "vscode.markdown.preview.editor"
  },

Please let me know if that works. Btw, it will set the right value if you go through right click on the file and then Open with..., then select Configure default....

[rubensa]

First, sorry, as this issue should have been opened at https://github.com/stateful/vscode-runme, not here, as it is an issue in a VSCode view.

As for the content of the issue, I must say that the VSCode default if for *.md files to be opened with the Builtin Text Editor (and you can "reset" that functionality, after installing Runme extension, setting the configuration I provided).

That said, the issue is that the RUNME NOTEBOOKS view shows, grouped by folder, all *.md files and it does not include in the list the *.runme files that I have associated with the runme extension editor.

NOTE: When I say RUNME NOTEBOOKS view I'm talking about the view labeled as "All Markdowns available to open as Notebooks" in the image from Notebook UX in VSCode doc.

[sourishkrout]

Thanks for the clarification @rubensa. Fine to file the issue here on runme versus vscode-runme.

We are working on replacing the Runme Notebooks panel with a newer implementation. The beta will be available shortly. I will leave this issue open to see what we can do about filtering out specific extensions.

[rubensa]

Thank you for the info @sourishkrout