Sublime Forum

**Alexey** · April 1, 2019, 10:15am

3203 with git enabled crashes as described for 3200. (Cmd-P when network volume ceased to be available).

**Alexey** · April 2, 2019, 7:18am

Right click -> “Delete file” does not work.

**Allan1** · April 2, 2019, 1:36pm

This new ST is eating all my MEM if i focus back to sublime. I have large py project with venv inside. Is there way to rever this version?

**Allan1** · April 2, 2019, 2:17pm

I found problem. I had some large db file opened and if i focused to sublime then it was reloading this file.

**wbond** · April 2, 2019, 4:49pm

Can you check your Console to see if an error is listed?

**wbond** · April 2, 2019, 7:11pm

2 posts were split to a new topic: Memory Leak on Switching Themes

**Alexey** · April 2, 2019, 7:23pm

  Traceback (most recent call last):
  File "/Applications/Sublime Text.app/Contents/MacOS/sublime_plugin.py", line 1050, in run_
    return self.run(**args)
  File "/Applications/Sublime Text.app/Contents/MacOS/Packages/Default.sublime-package/side_bar.py", line 28, in run
  File "/Applications/Sublime Text.app/Contents/MacOS/Packages/Default.sublime-package/send2trash/plat_osx.py", line 44, in send2trash
  File "/Applications/Sublime Text.app/Contents/MacOS/Packages/Default.sublime-package/send2trash/plat_osx.py", line 33, in check_op_result
OSError: Directory not found

**Alexey** · April 2, 2019, 7:27pm

Which (Directory not found) is not true of course, I can browser the directory in ST and open files there. Just to clarify again, this all happens when working on network volume which sometimes gets disconnected and reconnected. However previous ST version hasn’t have this problem.

**wbond** · April 2, 2019, 7:33pm

We haven’t updated the send2trash module in a long time, nor modified the delete implementation in side_bar.py. Sounds like the issue has probably been around for a while.

**Alexey** · April 3, 2019, 3:06pm

I can try with older build, how can I try it. May be the issue is old, but I have never noticed that before (not that I often delete files from ST GUI)

**OdatNurd** · April 3, 2019, 5:38pm

The error that you’re seeing is not telling you that the folder that you’re trying to delete from doesn’t exist, it’s telling you that when it tries to put the folder in the Trash, the Trash folder doesn’t exist.

I’ve seen that happen on Linux occasionally (where for whatever reason my user literally had no Trash folder). In this case since it’s a network volume, I would imagine that the problem is that the OS is trying to put the file into the trash folder on the network share and failing.

**braver** · April 3, 2019, 7:51pm

I don’t remember deleting files from the sidebar ever working for stuff on a network drive. I think I remember from 4~5 years ago that it didn’t work, and it definitely doesn’t work now (in between I worked some other place where I could work on stuff locally).

See also: https://github.com/hsoft/send2trash/issues/10, I guess it’s not fixed in the library either. I guess I could roll my own rm -rf ${path} command to work around it.

Edit, this works:

class ForceDelete(sublime_plugin.WindowCommand):
    # Delete file without sending it to thrash

    def description(self):
        return 'Immediately Delete File'

    def run(self, paths):
        for f in paths:
            if os.path.isdir(f):
                for v in self.window.views():
                    if v.file_name().startswith(f):
                        v.close()
                shutil.rmtree(f)

            else:
                v = self.window.find_open_file(f)
                if v:
                    v.close()
                os.remove(f)

**Alexey** · April 3, 2019, 6:11pm

ok, good point.
Still would be good to have ST to mimic native Finder behavior.

**milkman** · April 4, 2019, 10:59am

D’oh, I never noticed that the files are moved to trash instead of a hard delete

**BPL** · April 4, 2019, 12:36pm

Mmm, strange, my last comment was deleted … not sure if it was me who didn’t press the save button or the comment was banned from moderators lol,
anyway, I’ll assume it was just me being clumsy so lets try again

Thing is, I’ve been a happy user using the awesome 3176 release for months and after reading a lot of comments for the last days
talking how bad version >=3200 was I don’t see myself playing with the new version anytime soon.

It seems a lot of problems from that version come from the fact of having this new git integration.
I guess the end goal of that feature will be promoting users SublimeMerge. If this feature is optional
and you can disable the git integration completely (this is, not being forced to have any git background
tasks eating your CPU time and keeping ST lightweight) then everything fine as we’d be talking about
an optional feature (which is intended to use an external 3rd party tool). On the other hand,
if as a user you’ve been forced to live with something you may don’t need I think that’s
not cool at all.

For instance, I’ve got my own custom code/plugins that allow me to use git without having to run any
background tasks so I can keep ST as light&fast as ever, I’m fine with it and I wouldn’t
like to be impossed any new git integration nor using any additional software (even if SublimeMerge is
great, let’s assume it is).

Having an indexer running behind the curtains? Sure, that’s great&necessary as a lot of core plugins
will benefit from it, nothing wrong with it… But being force to have a git integration you didn’t ask
for? Then sorry but I think that’s not cool.

Of course, if this "show_git_status": false grants there will be no extra background tasks
spawned and the git integration is fully gone, then cool, nothing wrong with it of course
but otherwise forcing users with features they may or may not want… well, I think that’s
the same wrong approach than companies like Google do when forcing updates such
as gmail. Do you rememeber when they forced users to use a newer much worst version
than the previous one? That made a lot of people get angrier and considering not
using gmail anymore

Summing up, adding new features is of course awesome and I’m sure a lot of users
will love it but pleeeeeease, try to not force the minority of people and give them
the chance to choose between using or not the new fancy stuff. I’m sure I’m not the
only one who gets pissed off when wasting a lot of time because newest versions
disrupt their workflow with “subtle” but disturbing changes

Peace!

Ps. Sorry, I’m one those users who’re reliant to changes that may lead to waste of time

**djspiewak** · April 4, 2019, 1:54pm

"show_git_status": false and "mini_diff": false should pretty much disable all of the new git integration.

To be clear, there are no git background processes here. It’s done within Sublime in a fashion which is more lightweight than what git itself does, and also much more lightweight than what a lot of the alternative plugins do (e.g. GitGutter is much slower and does have background processes that it juggles). I’ve been using the git integration on the dev branch for quite a long time. I don’t feel pushed to Sublime Merge at all, and I’m manic about my editor remaining lightweight, fast, and energy-light. The new features have been an improvement in this respect (particularly since I’ve been able to drop GitGutter), and in no way a step back.

Obviously, a lot of this stuff is very subjective, but I think it was a really good set of features to add and generally very well executed. And if you don’t agree, you can just turn it off as I described.

**BPL** · April 4, 2019, 2:14pm

Thanks, If I ever upgrade I’ll have those 2 settings into consideration

In any case my only point from my previous comment was that if new features can be enabled/disabled you’ll keep all your users happy (no exceptions), that’s pretty much all I wanted to say.

To be clear, there are no git background processes here.

Jon talked about that very briefly here, If I’m not mistaken it seems there are 3 backgroun threads and the 3rd one can be disabled through user settings (if I’ve understood correctly)

and I’m manic about my editor remaining lightweight, fast, and energy-light.

Same here, I’m a total geek about control and if I can’t control fully the main tool I use to code that will bother me… And don’t get me wrong, I’m not saying that particular git feature or even SM are bad, probably they’re great (assuming cos I trust the team)… but some users like me are reticent to changes and we like to upgrade at out own slow pace. Even more, I tend to upgrade my software very very rarely cos I know 99% of times will take me time in one or another way.

Obviously, a lot of this stuff is very subjective, but I think it was a really good set of features to add and generally very well executed. And if you don’t agree, you can just turn it off as I described.

Good to hear, I was getting a little bit biased towards all those negative comments in the opened thread these days. it’s good to read positive feedback/reviews to have into consideration… Plus, the title of this thread has also been quite “dramatic”, so sorry if it’s scared the hell out of me

**djspiewak** · April 4, 2019, 2:20pm

Jon talked about that very briefly here , If I’m not mistaken it seems there are 3 backgroun threads and the 3rd one can be disabled through user settings (if I’ve understood correctly)

Threads, yes, not processes. Sublime Text doesn’t fork out to git, and its own internal implementation of Git’s status system is much more efficient than Git’s. So in other words, it’s not doing the naive thing that you might expect with git-diff and git-status (this is actually what GitGutter does); it’s considerably more efficient than that.

But yes, it can be disabled.

Good to hear, I was getting a little bit biased towards all those negative comments in the opened thread these days.

I think there are some legitimate issues with 3.2, particularly relating to network drives and/or people who do bizarre things, like throw their entire home directory into Git, but by and large I honestly believe it’s the best Sublime release yet. The improvements are excellent, but understated, as they should be.

**Alexey** · April 4, 2019, 2:40pm

I’m sorry for that. This is only my personal experience, but 95% of my ST work is happening via network volumes (BTW if sublime had native remote directory access ove SSH as Far manager used to have in the past that would be totally awesome and would remove a need for this buggy samba/apple client mounting experience). And with such pattern 3.2 release happened to be disastrous for me (till I switched git off).

**djspiewak** · April 4, 2019, 2:48pm

This may help: https://wbond.net/sublime_packages/sftp

Sorry, but 3.2 is the worst version ever (unless git integration is disabled)