I'm German, and using Sublime Text with a German keyboard (no surprise there).

This means that  a lot of the keyboard shortcuts are simply displayed wrong,   e.g toggle comment  is shown as "control + /" whereas on the German keyboard I actually need to use "control + #"

Now I can use "sublime.log_input(True)" in the console to find through trial and 

error what keys to use, but this shouldn't be necessary, and is, additionally, not very helpful regarding less often used key combinations.

Do I really have to poke around & then keep something as old school as a printed overview of the key mappings on my keyboard around?

I have a long sublime-completions file (about 2000 lines). The completions work fine, but words from the current file simply get ignored.

At first I thought the problem was about having characters like ( , : etc in the trigger, but it turns out it's a combination of characters + long file. Everything works great with a shorter file, but for a long file it only works if the trigger only has short words with nothing but letters.

I need to put those characters in the trigger so I can see which method I'll be "triggering". It is not possible AFAIK to put a description in a completions file, the way you can in a snippet.

Build system should recognize the env command as documented. Adding an env command to the build system results in a silent fail currently. If you open the console, you will see the following error : 

Traceback (most recent call last):

  File "./sublime_plugin.py", line 337, in run_

TypeError: run() got an unexpected keyword argument 'env'