Sublime Forum

Error after upgrading to ST 4

#1

Error loading syntax file “Packages/JavaScript/JSON.tmLanguage”: Unable to open Packages/JavaScript/JSON.tmLanguage

Any ideas?

0 Likes
#2

Has been answered at

0 Likes
#3

I’m having this issue now on my Mac and my Windows machine. I have tried clearing the cache out @ %LOCALAPPDATA%\Sublime Text 3 but I still get the following issue:

After launching Sublime text build 4113, I am able to open an existing JSON file without issue. However, creating a new document and pasting in some JSON gives the error detailed at the top of this thread.

Uninstalling Sublime Text, deleting traces from %APPDATA% and %LOCALAPPDATA% and doing a fresh install of 4 gives the same results.

0 Likes
#4

Does it happen in safe mode? Where are you pasting from?

0 Likes
#5

It’s the default output from the SFTP plugin’s Setup Serever function:

{
    // The tab key will cycle through the settings when first created
    // Visit https://codexns.io/products/sftp_for_subime/settings for help
    
    // sftp, ftp or ftps
    "type": "sftp",

    "sync_down_on_open": true,
    "sync_same_age": true,
    
    "host": "example.com",
    "user": "username",
    //"password": "password",
    //"port": "22",
    
    "remote_path": "/example/path/",
    //"file_permissions": "664",
    //"dir_permissions": "775",
    
    //"extra_list_connections": 0,

    "connect_timeout": 30,
    //"keepalive": 120,
    //"ftp_passive_mode": true,
    //"ftp_obey_passive_host": false,
    //"ssh_key_file": "~/.ssh/id_rsa",
    //"sftp_flags": ["-F", "/path/to/ssh_config"],
    
    //"preserve_modification_times": false,
    //"remote_time_offset_in_hours": 0,
    //"remote_encoding": "utf-8",
    //"remote_locale": "C",
    //"allow_config_upload": false,
}

If you copy and paste that in then the error pops up.

I can’t be positive but I’m fairly sure my Mac (M1) has only ever had Sublime text 4 installed on it and it has the issue too. Currently trying to set up a new Windows VM with a straight ST4 installation to see if it’s an upgrade issue, or a general one.

EDIT: Happens in safe mode too (subl.exe --safe-mode)

0 Likes
#6

Nothing happening here. Was there a safe mode warning when you started it? Note you need to first quit ST before being able to start it in safe mode on macOS.

0 Likes
#7

Yeah, the dialog box came up telling me it was in safe mode

0 Likes
#8

Aha!
If I copy that text back to my clipboard from here and then paste that in then I don’t get the error. Must be something invisible in that text that

SFTP for Sublime Text - an FTP, FTPS and SFTP client | Products | Codex Non Sufficit (codexns.io)

produces!?

0 Likes
#9

OK the issue is caused by the SFTP plugin specifying the old tmLanguage when it creates a new server. I raised a support request on their site.

0 Likes
#10

Hi @netizensmith
Did you receive a response?
I raised it with SFTP and no response yet.
@flexer

0 Likes
#11

No response here either, yet

0 Likes