Thomas Singer

Hm, there is no **Target Editor** option, neither in the context menu nor in the dialog which occurs when clicking **Other**.  

Thanks. Now I was able to finish exercise 1. When debugging the completion the connection often gets lost - maybe a timeout issue?

I wholeheartedly agree with that. I always waste time because I have to read the whole dialog's text to understand what "Yes" or "No" means, especially when exiting.

This option does not make any difference with respect to what screen is recorded - even after restart it records the wrong one.

I can't try any more because my notebook stopped working and I had to replace it with a mini-pc, so I don't have a dual monitor setup any more.

Hi @ttaylorr, For testing purposes I've added `echo "$@" >> /c/temp/smartssh.txt` to `smartssh.sh` and judging from the content of `/c/temp/smartssh.txt` Git-LFS definitely fails to execute this script (while Git succeeds)....

As an intermediate workaround we've switched back to using .cmd files on Windows. We need to avoid this because it causes problems with cmd.exe that is said to handle spaces...

I doubt I'd have the required knowledge about SWT internals or Windows API to solve that correctly.

IIRC, you need to add a SWT.Dispose listener to the display to get a notification for Cmd+Q on MacOS.

Even worse: at the time when the first edit related event `SWT.Verify` occurs, the selected character already has been magically replaced (`st.getText()` does not contain it any more). This looks...