Stop checking for updates

Question

In the elevated terminal (ctrl + `), every minute I received annotation lines:

Checking for updates: Sync Enabled: True Sync Timeout: 60000 Latest Update at: Thu Jan 1 00:00:00 1970 Thread is: Thread-4 Paths: [{'path': '', 'display': ''}] 

This interrupts me from debugging elevated plugins.

How to disable this Checking for updates ?

I tried 2 things to disable it:

• I added the line "update_check": false to /Users/maks/Library/Application Support/Sublime Text 3/Packages/User/Preferences.sublime-settings :

  {"ignored_packages": ["JavaScript console", "Harvest"], "update_check": false}

  And restarted the sublime. But nothing...

• I tried to find the line 60000 in all files of the elevated folder: /Users/maks/Library/Application Support/Sublime Text 3 But nothing good was found. Maybe 60,000 ms is the default value.

Update

Created function for searching text in packages and installed packages:

 searchInSubl() { cd ~/Library/Application\ Support/Sublime\ Text\ 3/Installed\ Packages; zgrep -e $1 *.sublime-package ; cd ../Packages; grep -R -e $1 * } 

With the help of this, I searched for different words: "Check for updates", "Synchronization is on", "Sync timeout", "60000", "Last update in", "Subject", "Paths". But nothing was found.

Apparently this update is an internal sublime 3 option. I don’t know how to disable it ...

Answer 1

Since Sublime Text 3 packages are in files with zipped .sublime-package , you need to use zgrep to search:

 cd ~/Library/Application\ Support/Sublime\ Text\ 3/Installed\ Packages zgrep -e "Checking for updates" *.sublime-package 

If nothing is found, try searching the Packages directory:

 cd ../Packages grep -R -e "Checking for updates" * 

We hope that one of them will correspond to the package. If so, add the package to the ignored_packages setting and restart Sublime.

If no searches work, try using other snippets of the message as a search query: "Sync Enabled", "Latest Update", etc.

Good luck

Note:

This is not the same problem as this one , where setting "update_check": false in your user settings does not stop Sublime Text 3 from displaying messages when a new assembly is released. This particular problem was caused by the fact that the plugin constantly prints a message on the Sublime console. As the OP commented below:

using turning off and on each plugin, the target plugin found, its name: "My Slices" in the Installed Packages folder.

Answer 2

My current version of sublime text 3 is 3083. Here the guys decided HERE .

Text version

Go to Settings → Settings-User → and insert this line of code at the end:

"update_check": false, or "update_check": false (without the last comma if the last element of the array). After that, press CTRL + S (on Windows) to save the file, or go to File -> Save

Image version

Answer 3

Two decisions, depending on what exactly you want to execute.

Since I'm not sure - maybe my English - so I give you two solutions.

BLOCK PACKAGE FROM UPDATE

As an example, I use Sublinter.

  Preferences> Package Settings> Package Control> Settings - User

... and add something like this to block the package:

  // Packages to not auto upgrade
     "auto_upgrade_ignore": [
         "SublimeLinter"
     ],

BLOCK SUBJECT FROM UPDATE

If you want Sublime to stop updating and you don’t trust application update blocking solutions, just use Nuke.

On Windows (the system I'm using) go to:

  C: \ Windows \ System32 \ drivers \ etc

... and open the file with the name "hosts".

You may need to move this file to the desktop, edit it, and move it back to its original location, since Windows may not allow any changes to it - even if you try as an administrator.

Then add this line of code to the hosts file:

  127.0.0.1 localhost www.sublimetext.com
 127.0.0.1 localhost sublimetext.com

The version with “www” will do as sublime sends updates from the location “www.sublimetext.com”.

The above code will prevent any connection of your device to "www.sublimetext.com", therefore there are no more updates.

This does not apply to packages; they need option # 1.