Sublime Forum

Hang when "Loading changes"

#1

I’ve got a single-user licensed Sublime Merge 2027 on Pop OS (basically Ubuntu 20.04). I have a repo with a Kicad project I’ve worked on in Sublime Merge on a bunch of different machines and it’s always been fine. On this new machine, when I open the repo it says “Loading changes…” and won’t show me any of the files I have modified. Clicking to older commits shows the files changed in those commits just fine. Running git status on the command line shows the modified files instantly, so the repo is fine.

Is there anything I can do to help debug this? The repo/branch in question is https://github.com/Neotron-Compute/Neotron-32-Hardware/tree/use_1598d_case

1 Like

#2

Also, if I stage files manually on the command line then open Sublime Merge, it all works fine and all the diffs show as expected.

0 Likes

#3

Oh. Unstaging one file in the UI was OK. When I then clicked “unstage all”, the one file I unstaged earlier remained visible and all of the other files disappeared from the UI - showing as neither stage or unstaged.

0 Likes

#4

Hi @thejpster,

Sorry to hear you’re having trouble using Sublime Merge.

Could you try running Sublime Merge in safe mode and see if the problem persists. You can do this by running ‘smerge --safe-mode’ via the command line.

Could you also confirm whether you have Sublime Text installed on this machine, and if so, whether you have any third party packages installed. I suspect a third-party syntax may be causing the hang.

Thanks,
- Dylan

0 Likes

#5

I do have Sublime Text installed, but it’s a fresh install so it had no packages - not even Package Manager.

Safe Mode doesn’t seem to help.

The minimum repo is:

  1. Clone the repo outlined above, and checkout the use_1598d_case branch.
  2. Open the repo in Sublime Merge
  3. Open the project in Kicad
  4. Open the schematic
  5. Change the schematic (e.g. move a part)
  6. Note that Sublime Merge does not show that diff of the file you just changed, and has also hung in such a way it cannot be closed, requiring you to “killall sublime_merge”.
0 Likes