Hi Metin,

> Maybe it'd be more clear if non-present commands would give a "Command not found" message,
> in stead of an "error in line 1", because that suggests an error in the command in stead of the
> command not being there.

The tricky part about this is that in addition to command names you can also put script code directly in a keyboard shortcut. When you get "error in line 1", it's because when it saw that the text in there didn't match an available command name it tries to execute it as literal script code to try and get it to do something.

- Michael