I'm using a package (in this case, MarkdownEdit) that has keybinds that are conflicting with those of my other packages.
Is there any way that I can either disable a given package's keybinds or prevent it from overriding other keybinds?
The easiest thing to do would be to create a Default (yourplatform).sublime-keymap file in Packages/MarkdownEditing with an empty JSON array to override the original.
Create a new JSON file with the contents
[
]
Select Preferences → Browse Packages… (or, on macOS, Sublime Text → Preferences → Browse Packages…) to open your Packages folder:
Linux: ~/.config/sublime-text-3/Packages or ~/.config/sublime-text/Packages
OS X: ~/Library/Application Support/Sublime Text 3/Packages or ~/Library/Application Support/Sublime Text/Packages
Windows Regular Install: C:\Users\YourUserName\AppData\Roaming\Sublime Text 3\Packages or C:\Users\YourUserName\AppData\Roaming\Sublime Text\Packages
Windows Portable Install: InstallationFolder\Sublime Text 3\Data\Packages InstallationFolder\Sublime Text\Data\Packages
The exact path depends on version and whether or not you upgraded from Sublime Text 3.
In that folder, create a folder called MarkdownEditing. Save your new JSON file in that folder as Default ($YourPlatform).sublime-keymap, where $YourPlatform is one of Windows, OS X, or Linux, depending on your actual platform.
Restart Sublime Text.
Now, all of the keybindings from MarkdownEditing should be nullified, giving you the originals that shipped with Sublime (or overrides you've already made).
I would like to add to a sublime package so that it can work right now (and then make a PR to the repo after).
I've installed Expand Selection To Quotes on Sublime Text 3. I go to Preferences\Browse Packages which takes me to ~/Library/Application Support/Sublime Text 3/Packages
I cannot find this package anywhere, so I look around the App's root and found it here: ~/Library/Application Support/Sublime Text 3/Packages/Installed Packages/Expand Selection to Quotes.sublime-package
This file is filled with hex values and is 2.2KB in size. I cannot modify this file and I'm not sure if it's the right file or if it's just a metadata file.
I ended up with a different solution than to modify the existing folder.
I forked the repo, made my code updates, then cloned it into the Packages folder. Sublime picks it up automatically plus any further code changes that you want to tweak.
So I decided to install Sublime text 2 alongside Sublime text 3 just to see if I could find where the Color Scheme - Default folder was for sublime text 2 and I found it without a problem (C:\Users\USERNAME\AppData\Roaming\Sublime Text 2\Packages\Color Scheme - Default). But when I went into the AppData/Sublime Text 3 folder to find the Color Scheme - Default folder it was nowhere to be seen. Does anybody know where this folder could be?
Note: I have checked in the installation directory (C:\Program Files\Sublime Text 3) just to make sure that I was not missing something.
under
C:\Users\USERNAME\AppData\Local\Sublime Text 3\Cache
On my installation. However the file inside is a .cache file and binary. I am searching the rest of my drive now for a more useful version!
I think the file (mostly xml format) you really want is this one 'Color Scheme - Default.sublime-package' under:
C:\Program Files\Sublime Text 3\Packages
As the forum post says at https://forum.sublimetext.com/t/edit-tmtheme-in-sublime-text-3/10999 - these package files are just zip files containing the .tmTheme files:
How can I install a sublimetext3 package manually, without the package control. I am trying to fix a bug in an existing package, therefore I need a way to test my changes.
what are the naming conventions to be followed when naming the zip file?
Where do I place it?
what other configurations I have to do?
Download the ZIP, and then place it in your Packages directory which can be found by doing Sublime Text -> Preferences -> Browse Packages...
what are the naming conventions to be followed when naming the zip file? Where do I place it? what other configurations I have to do?
This really depends on the specific package you are downloading. For some packages, you can name it whatever you want. For others, the name has to be exact. If you are downloading these packages manually from GitHub, I urge you to read the documentation in the README. They usually provide instructions for manual installation. For example, if you wanted to download the Spacegray theme manually, it tells you to download the ZIP, unzip the folder, and rename it to Theme - Spacegray.
Depending on your OS, your package directory might be one of these and for most of the packages, just extract the content to this folder (with it's root folder as the name)
Linux: ~/.config/sublime-text-3/Packages
OS X: ~/Library/Application Support/Subime Text 3/Packages
Windows: %APPDATA%\\Sublime Text 3
I am trying to fix a bug in an existing package, therefore I need a
way to test my changes.
I was in the same situation. The accepted answer didn't work for me because Package Control would automatically remove the folder. I found this to be helpful:
https://packagecontrol.io/docs/customizing_packages
Sublime Text 3 offers the most options for overriding a package. By
default, packages will be installed by placing a .sublime-package file
in the Install Packages/ folder. Then users may override individual
files in the package by creating a folder Packages/{Package Name}/ and
placing edited files in there.
Another approach is PackageResourceViewer, which allows you to extract and override individual files from packages, including the built-in packages.
The best answer I think, so far, is this one by #Andreas Haferburg.
The most-upvoted answer also has some really useful information, such as the link to the spacegray package which states:
Manual
You can also install the theme manually:
Download the .zip
Unzip and rename the folder to Theme - Spacegray
Copy the folder into Packages directory, which you can find using the menu item Sublime Text -> Preferences -> Browse Packages...
That is where I first learned about the existence of the Packages folder and how to find its path.
Using those answers together, plus putting in about 1 weekend worth of work into learning about how Sublime Text packages and syntax highlighting work, I wrote the following "Developer Notes & Package Development Tutorial", on GitHub, as well as these "manual installation" instructions.
In short, to "install a package" withOUT Package Control, all you need to do is put the package into your Sublime Text Packages folder, whose path can be found by going to Preferences --> Browse Packages.... The folder name can be anything. It only needs to match what is inside the Installed Packages dir (which is at the same level as the Packages dir) if you want to override an already-installed package which was previously installed by Package Control in "packed" (zip file) format.
The main link you should study, aside from my tutorial, is this: https://packagecontrol.io/docs/customizing_packages.
1. How to manually install a package
Here are some of the key quotes and instructions from my manual installation instructions and tutorial.
Again, note that I am only requiring that the name in the Packages folder be something specific like gcode in the instructions below because my instructions are intended to override a Package-Control-installed package the reader may already have installed. If you want to install for the first time, or make a new package, the folder name you use inside the Packages folder can be anything.
2. Manual installation
In Sublime Text, find the path to your Packages folder by clicking Preferences --> Browse Packages.... This will open up your GUI file manager to the path where Sublime Text packages are stored. For me on Linux Ubuntu 20.04, that's /home/gabriel/.config/sublime-text-3/Packages (even though I am running Sublime Text 4).
Now, extract this package to that folder.
Option 1: the GUI way: click the green "Code" button above --> "Download ZIP" --> save the zip file, extract it to your Packages path above, and rename it to gcode.
OR Option 2 [what I prefer]: the command-line way:
# --------------
# Option 2.A: clone the repo directly into your "Packages" dir
# --------------
# cd to the Packages dir (change this path according to your Packages path above)
cd "$HOME/.config/sublime-text-3/Packages"
# clone the repo
git clone https://github.com/ElectricRCAircraftGuy/sublime_gcode.git
# rename the repo dir to "gcode"
mv sublime_gcode gcode
# --------------
# OR Option 2.B [what I prefer]: clone the repo into wherever you want, and then
# symlink it into your "Packages" dir
# --------------
# clone repo into ~/dev
mkdir -p ~/dev
cd ~/dev
git clone https://github.com/ElectricRCAircraftGuy/sublime_gcode.git
# now symlink it into your Packages dir
ln -si ~/dev/sublime_gcode ~/.config/sublime-text-3/Packages/gcode
That's it! The gcode entry is now instantly available in your syntax highlighting menu.
Developer Notes & Package Development Tutorial
...
...
...
Sublime Text packages and syntax highlighting--how it all works
And here are some really important notes about Sublime Text packages and how Package Control works:
1. Sublime Text packages
Any folder inside of your Sublime Text Packages folder (found via Preferences --> Browse Packages...) is automatically instantly loaded by Sublime Text as a "package".
Packages installed by the Package Control package, however, come in two types:
Packed: most packages installed by Package Control are "packed" into a zip file named packageName.sublime-package and are located inside the Installed Packages dir which is at the same level as the Packages dir.
If you manually create a dir inside the Packages dir and name it packageName (to match the packed file above), then any files in it with the same name as those in the packed package will override those in the packed package. See the "Overrides" section here: https://packagecontrol.io/docs/customizing_packages.
Unpacked: any package which is installed in the Packages dir is unpacked.
Developers can tell Package Control to unpack a package installed by Package Control by placing a file named .no-sublime-package at the root of their repo. See here: https://packagecontrol.io/docs/submitting_a_package.
Unpacked packages are required if they contain binary executables which need to be run by the system, for instance, as they apparently can't run from inside the packed zip file.
2. Syntax highlighting
Hopefully I got all of this straight.
If you want to learn more about Syntax Highlighting in Sublime Text, and how it maps to scope entries in your Color Scheme, read my tutorial.
2. Test your changes
I am trying to fix a bug in an existing package, therefore I need a way to test my changes.
See also this section in my tutorial:
To modify and test changes to this package locally...
...in case you'd like to change it or contribute to it, follow the "manual installation" instructions above. If you have already installed it via Package Control, then what is in your /home/$USERNAME/.config/sublime-text-3/Packages/gcode folder will override what is in your /home/$USERNAME/.config/sublime-text-3/Installed Packages/gcode.sublime-package zip file which Package Control installed, so long as the folder and file names are the same.
Modify any files in the Packages/gcode dir as desired. Each time you save, the changes will instantly be reflected in all Sublime Text editors you have open. As a quick test:
Open a gcode file.
Click your cursor on some text in the file.
Use the Tools --> Developer --> Show Scope Name trick to see what the scope is for that text.
Open the corresponding *.sublime-syntax file.
Change or delete the regular expression in the match entry for that corresponding scope you just found, so that it no longer matches the text on which you placed your cursor.
Save the *.sublime-syntax file and you will instantly see the formatting of that text in the gcode file change.
Undo your change to the match entry and save again. The formatting will return to how it was.
Go to Preferences --> Customize Color Scheme, and add a custom rules entry for that scope, with new formatting for that scope. Save it and watch the formatting instantly change again. Delete that custom entry when done, if desired.
I'm using Sublime Text 3 as my editor in winSCP. How can i open the entire directories from Sublime Text 3 in winSCP ?
You need to install the 'SFTP' package in Sublime, create a sftp-config file to connect to your server and sync a remote directory to a local directory.
Install SFTP for sublime:
https://codexns.io/products/sftp_for_sublime/install
Sync: https://www.youtube.com/watch?v=g6NqBGHFfm0
If you don't want to sync the folders you can just right click on your sftp-config file->SFTP/FTP->Download Folder.
More details about sftp-config here: https://codexns.io/products/sftp_for_sublime/settings
It seems a bug in Sublime is that if Sublime is not the highlighted app while downloading it may cause problems.
that the files and folders appear in the sidebar but i think i found a answer for my question, namely i have to stall samba on my Linux Server or to install addon (SFTP) on Sublime Text.