I wanted to use it as a difftool as I already am fine with the git cli. I don't think it can do it? Maybe I could not find the documentation.
The thing is, I used https://www.kaleidoscopeapp.com/ on mac, which is just pure joy. Recently I'm trying to migrate into Windows with WSL and a decent graphical diff / merge tool is my pain point.
Any suggestions (or a way to use SM via CLI)?
Meld Merge (https://meldmerge.org/) is my favourite, due to being cross-platform. Works well for merging, and `git difftool -d`. Although I cannot get it to run decently on macOS nowadays :(
WinMerge (https://winmerge.org/) is also good, but Windows only.
But for a visual file comparison tool having giant light regions of the screen in dark mode actually affects functionality in a significant way. The “theming” doesn’t actually theme most of the interface chrome so only minor parts of it go dark, at least last I tried it a month ago.
I haven’t tried it in Windows dark mode. Might work better there. On Mac it’s probably using a Lazarus-based widget library, assuming it’s still written in Delphi, and it probably just doesn’t integrate with the system well.
To be clear, I paid Scooter Software for the pro version back in the 90s and about two years ago again. What I’m saying is I’m licensed for it and still have been looking for other apps because it’s not good enough anymore. I’m not just spitballing, unfortunately :(
First result :
> wrap Electron around this
You can do pretty much all of these things with Sublime Merge 2, so?
Doesn't get much closer to github-but-local than that I reckon.
Sublime Text's changelog (https://www.sublimetext.com/3) depicts the product as essentially abandoned, which matches my experience.
On the other hand, the page linked says that the team is expanding.
Sublime Merge and Sublime Text share a bunch of low-level code, various aspects like the syntax definitions and engine, the UI library, rendering backends, and a whole bunch more. The higher-level UI components and the exact way they are put together are different, but there is a lot shared.
All of that is to say that we've been busy at work on Sublime Text and have a whole bunch of new features, improvements and bugs fixes that are working their way towards a release.
Some of them are present in Sublime Merge since they are part of the shared code base, but a whole bunch aren't present in Merge since they are the sort of thing you deal with with editing and navigating source code, and not when dealing with version control.
We now have six engineers working at Sublime HQ between the Sublime Text and Sublime Merge products. So we have been growing, and we are still very much dedicated to both Sublime Text, and Sublime Merge.
For example, vim can offer modal editing, composable commands and a builtin commandline with ex-mode as it's killer-features. Emacs, well it's emacs, it always has much going, but lately it got some additional stuff like which-keys, hydra-mode and magits transient commands, which all innovate the editor-game quite strong.
Compared to that, ST seems to be quite conservative and only competing on a very small area.
From my perspective, Sublime Text isn't looking to become something different. Instead we are continuing to make a well-polished text editor that is fast and can be extended in many ways. As you've noted, we've added a lot of polish, but also added some pretty significant features, and continued to lay the ground work for more smart, out-of-the-box functionality. Some of the things may not jump out at you in terms of reading a changelog, but you'll feel them as you see how they can help you to navigate and write software.
Many users want or need their edge cases more well handled. Package developers want to have access to more information and be able to influence more of the behavior of the application. We daily engage with active community members to better understand how they want to add features, and are regularly working on ways to make that possible. However, the biggest number of users are helped by the features provided in a default install and that require no configuration. We've continued to put work into those areas to make Sublime Text excellent and easy-to-use, from the moment you open it.
I'm not particularly interested a feature by feature comparison, but I think upon a close look, you'll find that Sublime Text generally provides excellent, high-performance implementations of many features that get less attention in other products. Some people really appreciate the polish, the speed, the things that just work. Other people want more automation and deep language integration. Some people want a single interface that contains many different tools. Through a combination of default functionality and plugins, we can cover a fair bit of that. Clearly we aren't trying to be everything to everyone. Luckily for users there is a healthy market of tools to write software, and we'll continue to be a part of that and to build a product that we (and many, many others) love to use.
Our products are implemented in C++, and we utilize platform-specific APIs to integrate with the OS in the ways that make the most sense.
In terms of the UI, however, we have a custom library with our own controls, control structure, event handling, rendering, etc. We only use native UI for menus, file pickers and title bars. We do, however, use OS-provided font layout and rendering APIs so that text looks like other apps on your OS.
By implementing only what we need, using a language with low overhead, and making a point of writing code that is efficient, we can generally accomplish excellent performance. This, combined with trying to following platform conventions and taking the time to integrate with the OS APIs, provides a UI that feels snappy and generally doesn't look out-of-place, such as most Java UIs.
Unlike VS Code, not all software can be open sourced and provided for free while many paid software engineers are employed to actively develop it by a trillion-dollar corporation. Software that is fast, native and cross platform without ads costs money to make. I support it with my dollars (I use SM and ST). Fortunately, there is a healthy market for GIT GUI clients as seen by Git Kraken, Source Tree, Fork, Sublime Merge, etc.
The GitLens website asks for monetary support and sponsorship front and center. If that's the way you prefer, that is perfectly OK. That doesn't automatically make it a better product.
i'm a big fan and would love to see an early peek at what's coming, and would be happy to do bughunting or feedback if that's what the team is looking for.
Sublime Text is not abandoned. Having a glance at Sublime Text 3's update history, as well as the forums, will alleviate any such concern.
>On the other hand, the page linked says that the team is expanding.
The linked article discusses Sublime Merge, a different product.
Based on the history, in the last solar year, the builds have been:
- 3211, Oct/19: 4 fixes, plus what I suppose is a functionality, for Mac
- 3210, Sep/19: 1 fix
> The linked article discusses Sublime Merge, a different product.
I'm aware of it, but my question still stands, as there is no information in the typical information channels (i.e. blog, twitter).
If you write that the forums says so, I trust that, but not updating the blog and twitter (about ST specifically) is generally not a good sign.
* Auto Complete: Ranking quality improvements
* Auto Complete: Added auto_complete_use_history setting to control if previous choices are automatically selected
* Added additional settings to control the status bar: show_sidebar_button, show_indentation and show_syntax
* Added relative line numbers, controlled by the relative_line_numbers setting
* Color Schemes: Added support for the underline font style
* Color Schemes: Added new property, inactive_selection_border
* Added setting hide_pointer_while_typing
* Console now uses Python syntax highlighting by default
* Windows, Linux: Added Shift+F10 key binding to open the context menu
* Fixed folder dragging in the sidebar
* Further improvements in layout preservation when programmatically editing preferences
* API: View.add_regions() calls that add an underline now have that underline applied to whitespace characters
* API: Added sublime.INHIBIT_REORDER
* API: Window.new_html_sheet() now accepts the sublime.ADD_TO_SELECTION flag
* API: Window.new_html_sheet() no longer accepts cmd and args parameters
* API: Fixed a regression in View.split_by_newlines()
> - 3211, Oct/19: 4 fixes, plus what I suppose is a functionality, for Mac
> - 3210, Sep/19: 1 fix
I don't see what you're trying to point out. What about bug-fix updates points to the software being abandoned? I'd argue that it demonstrates the exact opposite.
>I'm aware of it, but my question still stands
>not updating the blog and twitter (about ST specifically) is generally not a good sign.
Perhaps; perhaps not. You may be putting too much weight in their "social" presence instead of looking into the factors that matter most such as ongoing support and development. The team behind Sublime * is tiny compared to other software enjoying similar popularity. I suspect effort is primarily focused on development of the next major version of Sublime Text, the ongoing support of Sublime Text 3, Sublime Merge's newest release, and other projects we don't know about. I can understand a lull in Twitter/blog/etc. presence.
Why is that concerning? I'm no longer on top of Sublime Text's outstanding bugs as I was some time ago. Is the backlog of issues/severity such that an increased release cadence is necessary?
what else do you think it needs? keeping in mind that it's a text editor, not an IDE
then, the last time I had a look at the plugin API, again, there were significant limits in the events systems (I don't remember which; I think they were again related to the tree panel).
I have a different porcelain which I prefer, but if i wasn't an emacs person (and thus, a magit person), i'd be willing to pay for this just like i once bought sublime text.
Nice to see a native app keep chugging along.
and still feel most at home there.
I'd guess the biggest reason to use Sublime Merge over a VSCode extension is that it's a small, very fast, native app. I've used it before when wanting to, e.g., search my git history for a change I'd made (IIRC a function name I remembered but which was no longer in the codebase). It's just snappier in general than VSCode. But I use command line git rather than any VSCode integration, so for the most part that serves me well enough anyway.
My last straw has been having to use a specialized plugin to workaround a bug that hasn't been fixed in years.
There may be platform reasons not use VSC - I don't argue about those - but as things are, VSC is an immensely more polished product.
Says who? Most products don't have public releases of anything and don't give details for their internal development but once a year or once every 1.5/2 years.
Sublime Text has been this way since 2010 at least, and yet, from release 1.0 we eventually got to release 3.2 (with 4.0 in behind the scenes dev). Every time and then, a new release / fix lands.
Sublime Text development is not halted. What has given you the idea that it halted more than a year ago?
>My last straw was being forced to use a plugin to fix a bug that hasn't been fixed in years.
What's the bug?
(As I wrote in another comment) The typical information channels (blog, twitter, development builds page) don't say anything.
I take the point that one can gather from the forum, the fact that there is ongoing development, but I think it's reasonable to be at least perplexed when a company is not active on the standard information channels, while at the same time expanding the team on a different product.
> What's the bug?
Files navigation panel goes out of whack, while switching between the editor and it with the keyboard; any keyboard-only user will experience it (although ST can't be used keyboard only, due to the inability to open a popup in the file panel via keyboard).
Somebody opened a bug open a long time ago, and somebody else wrote a snippet (a plugin, I suppose) to use as workaround.
The Sublime team seems to prefers 1 big and stable update vs 12 smaller and possibly less stable updates. It has its advantages and disadvantages.
Regardless, Merge is still the best Git GUI out there and this update just made it better. And Text is my favorite simple text editor out there (though I do prefer using a full IDE for actual development)
They probably don't want people to stop buying ST3 while they're waiting for ST4...
Unless you're seriously suggesting that someone would stop using the Sublime Merge tool just to use vscode IDE for the sole function of git repo management.
In which case, yeah, don't do that
I tried a bunch of clients, including "Sublime Merge", but none of them seem to have what to me, seems like a better way of looking at diffs where the changes are interspersed across an entire function.
... maybe I'm not looking for the right "name"? any pointers in that direction would help as well.
The google search that may help would be for "merge tools".
are there other git gui's which can do that? (surely there are, but I don't know them)