Sigil shortcut clash with Zoom shortcut in W10

[philja]

After updating Sigil in my Windows 10 box to 2.5.0, I checked out a few things and that involved using the focus shortcuts.

To my surprise, Ctrl+Shift+C opened up an app to record a video clip instead of placing the focus in Sigil's Code View. I tracked that down to Zoom. Earlier in the day, I'd had a couple of Zoom meetings after which I shut Zoom down. But that still left four Zoom processes running as background processes.

One of those was called 'Zoom Workplace' and that was the one which had to be closed down to get Sigil's shortcut available to Sigil.

Investigation inside Zoom's settings showed that the Clip recording option could be de-selected which I did. And thereafter, there was no more interference by Zoom.

Ctrl+Shift+T and D are also potential shortcuts which can be selected in Zoom but appear to be unselected by default. I tried activating them and, sure enough, they interfere with Sigil if the Zoom Workplace process is still running in the background. They don't launch any unwanted app but simply take priority and prevent Sigil's focus from moving to the TOC or Clips.

Interestingly, the shortcut options inside Zoom on linux seem to be far, far fewer. Only Ctrl-Shift-D exists and the few shortcuts that are listed appear to be all activated by default - no check boxes to select or deselect. But Ctrl+Shift+D doesn't5 worry Sigil on linux.

Not a Sigil problem, but noted in case it happens to anyone else.

[KevinH]

Interesting that closing Zoom leaves 4 zoom processes that are still listening to keystrokes. Not a good thing at all. I would write a script to run that kills all Zoom leftover processes asap and run it on every shutdown of Zoom.

You should be able to edit Sigil shortcut preferences to change them, but that will not help stop zoom doing keyboard watching or god-forbid logging after supposedly being shut down.

[retiredbiker]

Zoom does indeed leave bits running. Quit some time ago, I started running "pkill zoom" just as a habit after a zoom meeting, so it did not mess other things up.

[KevinH]

Originally Posted by retiredbiker

Zoom does indeed leave bits running. Quit some time ago, I started running "pkill zoom" just as a habit after a zoom meeting, so it did not mess other things up.

Keyboard monitoring by software that could potentially create a log and use network access to send it someplace is definitely not a good thing.

Using pkill zoom is a very Smart move!