Ok, that makes sense, thanks.
VS Code’s implementation works very well. I use it almost every day with VS Code running in Windows but my repo located in WSL or on a server accessed via SSH. There are good graphics showing how it works here:
Maybe Sublime could implement something like this? Being able to use Merge for a remote server would also be huge for us.
For WSL, I usually rely on VSCode’s built-in Git support plus the Git Graph extension.
VSCode’s Git also suffers the same problem of ‘not reloading changes automatically’. Unlike SMerge it does have a consistent cross-platform GUI, no visual bugs, and wouldn’t suddenly force close or freeze on me.
I do have a SMerge license (just renewed today, too) but of late I’m relying on VSCode Git and LazyGit a lot more. I use SMerge when I need to commit specific hunks of text - VSCode isn’t very precise about that yet.
I haven’t used VS Code to pull/push/commit/etc., but if I save a file in VS Code, git in WSL knows it was changed. If I change a file in WSL, the change is reflected in VS Code without me having to do anything. If I change a branch in WSL, the branch change shows up immediately in VS Code. When I say “VS Code” here, I mean VS Code running in Windows and connected to WSL with the WSL extension, as described in the first link here:
Sublime team, is there any reason the approach described there can’t be implemented for Sublime Merge?
Sublime team, is there any reason the approach described there can’t be implemented for Sublime Merge?
Other than a large amount of work needed to separate all the IO so it can run on a separate executable and send it over the network, no there’s no reason it couldn’t be implemented the same way.