Jrnl: Electron deprecation warning when using vscode

[g-berthiaume]

Bug report

This is more a heads up than a bug report:
When using vscode as my jrnl text editor, deprecation warnings are raised in the terminal:

(node:14320) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information
(node:3232)  Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information

• Please tell us about your environment:
  jrnl version v2.2
  pip
  windows10 (using cmd)

[micahellison]

I get the deprecation warning with Visual Studio Code too, by running it from the command line and looking at the terminal once it loads. It's a non-issue for jrnl and hopefully should be resolved by the VS Code team soon.

[g-berthiaume]

I understand. I was hopping maybe a vscode flag could change this behavior.
Regards.

[micahellison]

Oh, I see, my apologies.

I don't think there's a solid workaround for this, though. I tried suppressing errors by piping them to nul in the editor field of the jrnl yaml config, but that doesn't seem to do anything. And I don't see any VS Code flags that would be of use.

I also tried playing around with a batch file using the start command to invoke it with /wait, so the annoying errors would at least get piped to a different console window, but I didn't have much luck.

The next best solution I can think of feels a bit overcomplicated, but conceivably, one could create a launcher program in whatever language one is most familiar in to take the command line parameter and pass it to VS Code while suppressing the warning messages or keeping them in a separate window. But at that point, I think I would choose to just live with the warnings or pick a different editor.