Sublime Forum

**tamj** · September 23, 2025, 10:43am

I’m building the back end of a website, e.g. doing Node.js scripts things like authentication, logout, setting user preferences, etc.

Whenever I save a script after editing with CTRL+S, I get the following sort of message in the bottom console output area:

[Errno 2] No such file or directory: 'node'
[cmd: ['node', '/home/sandbar/.config/sublime-text/Packages/JSLint/linter.js', '--bitwise', '--browser', '--es6', '--eval', '--for', '--fudge', '--node', '--this', '/home/sandbar/Desktop/nodeapp-local/handlers/authen.js']]
[dir: /home/sandbar/Desktop/nodeapp-local/handlers]
[path: /usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin:/home/sandbar/.local/share/JetBrains/Toolbox/scripts]
[Finished]

Taking the output at face value, it makes no sense. I never asked ST to save my file to a file/dir called ‘node’.

Does anyone here develop for Node.js on ST and have similar behavior ?

EDIT

@bschaaf:

The following is the only key-binding to CTRL+S in my ST setup:

{ "keys": ["ctrl+s"], "command": "save", "args": { "async": true } }

**deathaxe** · September 23, 2025, 9:30am

Looks like a plugin attempting some action on save.

**tamj** · September 23, 2025, 9:35am

I see.

Usual routine of disabling plugins one by one to find the one doing the jig ?

**bschaaf** · September 23, 2025, 10:18am

I’d also check your keybindings to see if there’s something else bound to ctrl+s.

**tamj** · September 23, 2025, 7:38pm

Looks like JSLint is the package causing the hassle. Once disabled, CTRL+S shows no alternative effects.

I wish I could cure ST’s recently acquired sluggishness as easily

**bschaaf** · September 24, 2025, 1:24am

I wish I could cure ST’s recently acquired sluggishness as easily

What do you mean by this?

**tamj** · September 24, 2025, 7:41am

@bschaaf

Lately (over the last few months) my ST (version 4200 on an Ubuntu 24.04 platform) has been a bit slow to react to simple user actions like changing page tab, page saves - especially multiple saves with Save All - and other basic manipulations. One really annoying thing is the 3-4 seconds needed to deselect a selected section of code (e.g. a block of code that was just previously copied to another page) after clicking on the surrounding text. As someone who uses single-page app processes, I need to have separate page-states on the server for every page-state navigable to the user in order that users may successfully use the browser’s Forward, Back and Refresh buttons. So I am often copying the same content across 10 - 20 .html pages. Delays in deselecting selected blocks of code slows this process down. I know, it’s time that I automated this with Gulp.js.

It is strange as ST has previously, from the beginning of my use of it, been a fast response editor that never jammed on rapid use. It was like a single-page web app compared to a traditional multi-page one.

I am not sure what is causing the sluggishness but if I can’t fix it with Google suggestions I will post an issue here. The sluggishness isn’t a show-stopper but if you like to work fast when in a creative mood, it can be a drag on progress.