Skip to content

Commit 7f3aec1

Browse files
[Chore] Update README.
Currently, it seems there are some issues with loading browse.py and the settings when a package installs, so just add an instruction to restart after the package is installed.
1 parent 2778726 commit 7f3aec1

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,8 @@ A Sublime Text package that allows a user to view all the available core/plugin
1212

1313
There are several ways of installing & using this package, which are listed below (from the most preferred way to the least preferred way)
1414

15-
1. Use `Package Control: Install Package` and search for `CommandsBrowser` & install it.
16-
2. Use `Package Control: Add Repository`. Copy the GitHub url for this repository (without the `.git` at the end) and enter it into the input panel that pops up at the bottom when you select `Package Control: Add Repository`. Now use `Package Control: Install Package` and search for `CommandsBrowser` and install it.
15+
1. Use `Package Control: Install Package` and search for `CommandsBrowser` & install it. Restart ST after you install it.
16+
2. Use `Package Control: Add Repository`. Copy the GitHub url for this repository (without the `.git` at the end) and enter it into the input panel that pops up at the bottom when you select `Package Control: Add Repository`. Now use `Package Control: Install Package` and search for `CommandsBrowser` and install it. Restart ST after you install it.
1717
3. Simply `git clone` this repository in your `Packages` directory.
1818
4. Whenever a new tagged release is pushed, grab the attached zip file for that release, rename it to remove the `.zip` extension & add `.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).
1919

0 commit comments

Comments
 (0)