This is the default for Windows and Linux, but not on Mac. Please add the following to the default key bindings of Mac:

{ "keys": ["home"], "command": "move_to", "args": {"to": "bol", "extend": false} },

{ "keys": ["end"], "command": "move_to", "args": {"to": "eol", "extend": false} }

I'd like to run

path\to\sublime_text.exe --project Y.sublime-project

from a batch file, but the behavior is weird:

• If I had another project X open in the previous session, Sublime will open X and Y in separate windows
• If I had all projects close in the previous session, Sublime will open only Y
• If I had project Y open in the previous session, Sublime will open Y and an empty window

Can this please be streamlined, or maybe there should be more command line parameters to affect what is opened from the previous session, e.g. `--no-previous-session`.

For example:

You're working in a GIT repository, without a "*.sublime-project" file.

CTRL+P (Cmd+P; Goto Anything) should work based on this GIT repository. You're project-root is the ".git" folder and in ".gitignore" are files to be ignored.

Now it's not necessary to create a "*.sublime-project" for your project. 

At the moment setting "close_windows_when_empty" results in the following behaviour that I found unexpected, and request be changed.

Scenario:

Set "close_windows_when_empty" to true.

Open 2 files in a sublime window. Drag one tab to a new window.

Drag that one tab from the next window back to the original window

Expected behaviour:

The window now has no tabs or open folders, it should close.

Behaviour:

It doesn't close.

Hi,

It would be nice if a new sub-entry of the 'File' menu main entry is created: it's allow to save the current file with another file name without exiting the current file (very useful when creating a lot a files from the same base with a time stamp for example).

Thanks

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'