I am using sublime text 2 (version 2.0.2) editor on cent os 6.5. Recently I started facing many issues, but one major issue is it does not remember the open files after closing and opening the editor window. Earlier it used to not only remember open files but also unsaved edits, after testing online suggestions I still could not resolve this issue, any suggestions would be of great help.
"hot_exit": false,
"remember_open_files": true,
"create_window_at_startup": true,
these are my current parameters in Preferences -> Settings - Default
I could solve this issue myself following this helpful link Reverting to fresh install state. Although that link has not worked for me, I just deleted sublime_plugin.py from my /opt/Sublime Text 2 directory then it works fine. So it seems that sublime starts misbehaving after adding new packages. In fact, I had deleted everything inside ~/.config/sublime-text-2 before sublime_plugin.py (it did not help though) not sure whether that is required, not to mention you can try after taking a backup
Related
I have been going back and forth searching why and how to fix this particular problem regarding Vscode freezing up my whole working space including the host, when I am in the middle of working on a project or immediately I open it. Preventing me from finishing up my projects. I am using Linux on VirsualBox. Is there an actual way I can fix this problem? I know there have been other developers facing similar issues, but I have not being able to find a clear answer to solving this problem still.
Some things to try:
Disable all your extensions. There are some extensions which might not play nicely with VirtualBox
Disable settings sync
Do a complete reinstall VSCode
If these fail, I would take some steps to verify that it is in fact VSCode that is causing your workspace to freeze.
VS Code by default searches the many thousands of files in node_modules or other similar directories.
You can prevent this behavior by simple edit your settings.json file paste this code.
"files.watcherExclude": {
"**/.git/objects/**": true,
"**/.git/subtree-cache/**": true,
"**/node_modules/*/**": true,
"**/.hg/store/**": true
}
So I recently installed Materialize package on my Sublime Text 3 just to try it out, and didn't like it. So I went ahead to remove it. After removing, My Sublime got all messed up. I couldn't see my files. Can't open package control. The screen itself is messed up. I tried Uninstalling and Reinstalling many times, and I'm still experiencing the same problem.
Please help me fix this, Thanks!
Most likely your settings still refer to the old theme, which doesn't exist any more. You can follow the instructions at https://www.sublimetext.com/docs/3/revert.html to revert to a clean state, or just edit your Packages/User/Preferences.sublime-settings file to remove the old theme setting. (The Preferences menu -> Browse Packages will be visible even when you are having theme problems.)
I am using Sublime Text 3 on my Mac (10.13.2)
The Preferences menu is always greyed and not usable. (even on restart)
Any idea to solve that?
Thanks
Paul
On macOS, I deleted the file Package Control.last-run in /Users/cookedapple/Library/Application Support/Sublime Text 3/Packages/User and restarted Sublime Text 3. The problem was resolved.
There have been some suggestions that third-party Mac apps may be causing issues. So you may try restarting Sublime Text – I guess you have already done that before looking for a solution, try to do that again after each of the following steps:
Restarting menu bar Bartender or SecondBar if present
Reinstalling latest installed ST packages
Delete(https://stackoverflow.com/a/48398420/880188) Package Control.last-run, i.e. via Terminal: rm ~/Library/Application\ Support/Sublime\ Text\ 3/Packages/User/Package\ Control.last-run as mentioned in the other Answer
Restarting the computer
A user has figured out a reliable way to reproduce this (see Kronuz' comment from 6/19/18 on the issue tracker).
It seems to be caused by packages containing a large amount of files. There might be other causes as well, but hopefully with at least one reliable way to repro, the devs will come up with a fix.
I was writing some HTML in Sublime Text 2 and I noticed that the auto complete feature was no longer working. Just so we're clear, I'm not referring to the dropdown menu that suggests elements but rather the tag completion. Normally what happens is if I were to type an opening tag all I'd have to do is type the beginning of the closing tag and it would auto complete the tag which obviously saved a lot of time but now it's not working for some reason. I do have package control installed along with quite a few extensions but I heard that this feature is actually built in. I deleted ST2 off my computer and re-downloaded it, and it still isn't working so I'm not sure what else to try.
Is this feature really a default feature in Sublime Text 2? If so, why wasn't it working when I re-installed Sublime Text 2?
I'm on a Mac and I'm running Yosemite.
Thank you for reading.
Installed Sublime Text 3 and it works again.
Today I tried to made "Code Cleanup" of single file in ReSharper 6.0 (VS 2010). The Code Cleanup dialog did not show up so I tried again.
I then discovered, that the feature is grayed out and when I press hotkey for Code Cleanup, the notification area shows that the "command is not available at the moment".
Even the Code Cleanup settings are hidden. The panel where settings should be shown says that the settings are solution-specific and thus a solution needs to be opened (although it is, however).
All other solution-specific settings and features work, except for Code Cleanup.
I want to avoid re-installing ReSharper or resetting its settings, because otherwise I would need to set it up again (long and annoying work of setting all the options as before re-install).
I am afraid that backing up settings and restoring it again restores the problem as well.
Any suggestions?
Suggestions:
Ensure that the file that you're trying to cleanup is included in your solution.
Try to reopen solution (close and then open again).
Upgrade to 6.1.1, maybe its fixed there.
File a bug report at http://youtrack.jetbrains.com
Both ReSharper 7 and 8 seems to work OK.
I know this is an old answer, but I found a little more insight on this. According to Jerrie Pelser in this blog post from last year, this may have to do with the file being part of a NuGet package. In my case, this was definitely it!
In case of link rot, basically the post mentions that ReSharper will avoid refactoring/code cleaning for files it detects were added as part of NuGet packages. This is similar to how it will not allow code cleanup for generated code.