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. Use Preferences: CommandsBrowser Settings from the command palette.Use Preferences -> Package Settings -> CommandsBrowser -> Settings from the main menu.You can change the settings in 2 ways (Both will open the same side by side view for settings). This package should be upto date with commands as of ST Build 4131 & SM Build 2069 SettingsĬommandsBrowser adds several settings for various customizations and filtering of commands which are documented below. 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. Similarly, you can use CommandsBrowser: Open Wiki to open the wiki of the repository in the default browser to view in depth documentation on certain commands. If you want to view the documentation for the package, simply use CommandsBrowser: View Documentation which will open the README for the project in your default browser. 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. You can also hold down ctrl while selecting a command to copy it's signature to clipboard.ģ. Selecting one would bring up a panel that would show the documentation for that command. This will show you all of the core commands that are present in Sublime Merge. CommandsBrowser: Browse available Sublime Merge core commands. You can also hold down ctrl while selecting a command to copy it's signature to clipboard.Ģ. This will show you all of the core commands that are present in Sublime Text. CommandsBrowser: Browse available Sublime Text core commands. This package provides 3 items to the command palette.ġ. For more information, refer the CONTRIBUTING guidelines Documentation How to use this package ? 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). Whenever a new tagged release is pushed, grab the attached zip file for that release, rename it to remove the.Simply git clone this repository in your Packages directory.Now use Package Control: Install Package and search for CommandsBrowser and install it. 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. Use Package Control: Install Package and search for CommandsBrowser & install it.There are several ways of installing & using this package, which are listed below (from the most preferred way to the least preferred way) A Sublime Text package that allows a user to view all the available core/plugin commands for Sublime Text and Sublime Merge, along with their documentation/source.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |