![sublime merge packages sublime merge packages](http://cdn.designrshub.com/wp-content/uploads/2015/03/sublime-text-packages-07.jpg)
- Filters to show only window commands.This setting allows a user to filter the plugin commands based on the type of the command. The default value for this setting is "all". "3.8" - Show plugin commands from the 3.8 host only. "3.3" - Show plugin commands from the 3.3 host only. Valid values are "all", "3.3" and "3.8" "all" - Show plugin commands from both hosts. This setting allows a user to filter the plugin commands based on the host. The default value for this setting is false. This can be helpful when you quickly want to glance the documentation for multiple commands at once and not have to close & reopen the panel every time. When set to true, automatically opens the core commands documentation panel as you navigate through them. auto_open_doc_panel_on_navigate ( Boolean) The package ships with necessary helper files for users of LSP + LSP-json to take full advantage of intelligent autocompletions for settings. This package should be upto date with commands as of ST Build 4122 & SM Build 2062 Settings So, together, ST + SM command list should be a good overview of the total number of commands present in both applications together. They are not listed in SM, because they are already listed in ST. However, since Sublime Text & Sublime Merge share a common codebase, there is a decent possibility that a good number of ST commands work in SM as well. The list of Sublime Merge commands are limited to what is specific to Sublime Merge (95% of which is git related). As far as I know, it should be fairly close to a complete list (It's probably the most comprehensive public list available). Since the core command list is not exposed by ST like plugin commands are, the only way to keep track of it would be to manually maintain a list of commands and show it. Selecting one would open the corresponding plugin file & navigate to that location where the command class is implemented. This will show you all of the plugin/package commands that are present in Sublime Text. CommandsBrowser: Browse available plugin/package commands.Selecting one would bring up a panel that would show the documentation for that command.
![sublime merge packages sublime merge packages](https://forum.sublimetext.com/uploads/default/optimized/3X/1/0/1071a9b451ae7d2697827d6ac32f5d8d603b9ec0_2_1380x344.png)
This will show you all of the core commands that are present in Sublime Merge.
![sublime merge packages sublime merge packages](https://forum.sublimetext.com/uploads/default/original/3X/a/2/a24f7129cca70ed79b7a4a6db71fdeeeafbf260f.png)
If you are interested in contributing to this repository, then you need to follow (3). sublime-package extension and drop it into your Installed Packages directory (You however, loose the goodness of Package Control automatically updating the package, when there is a new tagged release).
![sublime merge packages sublime merge packages](https://forum.sublimetext.com/uploads/default/original/3X/d/8/d88db5a2d4e87d111582f837e2b5d4e9679d2c88.png)
git at the end) and enter it into the input panel that pops up at the bottom when you select Package Control: Add Repository. Copy the GitHub url for this repository (without the.