>You can also hover over most buttons to see which git command it will run.
I really like this feature.
Show HN: Sublime Merge – A Git client from the makers of Sublime Text
221–230 of 362 posts
Re: Show HN: Sublime Merge – A Git client from the makers of Sublime Text
#222I've been using Tower but I may switch to this since Tower switched to a subscription model and I'm a fan of Sublime Text.
Re: Show HN: Sublime Merge – A Git client from the makers of Sublime Text
#223Earlier quoted context omitted.
> doesn't have features such as tabs The lack of tabs is a feature for some of us. After all, why have tabs when you can have tmux? :)
I needs to connects to multiple servers at the same time, and tmux sessions shouldn't be stacked. How can I do that without tabs?
Use multiple panes and/or windows? It's a terminal multiplexer, each panes is a separate terminal, just like tabs.
Re: Show HN: Sublime Merge – A Git client from the makers of Sublime Text
#224Looks great Jon, happy you are expanding the Sublime family. Can I suggest Sublime Terminal as a possible addition? I'd happily pay for a decent terminal experience on Windows and with your cross platform toolkit it looks like you could deliver that. ConEmu et al just don't do it for me.
I would keep an eye out on alacritty. It's a blazingly fast gpu-accelerared terminal emulator for Unix (currently) written in rust. According to their 0.2.0 announcement post, where they added scrollback support, Windows is next on the Roadmap.
It's fast in the throughput sense. Typing latency is much worse than Terminal.app
Re: Show HN: Sublime Merge – A Git client from the makers of Sublime Text
#225One thing I really miss with diff tools like this, is the ability to review multiple non-consecutive commits on a single branch, without including all commits in-between.
Example, lets say I want to review commit A and D: HEAD - A - B - C - D - E...
In most diff/review tools, when I select these commits in the GUI, it would show me all changes that have been made in commit A, B, C and D. What I actually want is for the viewer to filter out or atleast distinguish between the changes made in commits I selected, and the commits that are made in-between (in this case, B and C). This could of course lead to conflicts where the commits in-between have modified the same lines of code, but I really don't think this is a problem in 99% of the time.
This would really help the review workflow in scenarios where branching and pull request are not always used.
Too often, I have put down the time to review a single commit, only to find out that the next commit in the same task already fixed the things I noted in the first. reviewing both of them at the same time would save a lot of time.
Re: Show HN: Sublime Merge – A Git client from the makers of Sublime Text
#226$99 for this? When there's git cli, magit, fugitive (which you should be using if you're really really in need of a GUI (and which is also better than whatever the demo is showing))? I'm all for paying for your tooling if you can afford it but overcharging much?
Sublime Text is close to being the only piece of perfect software. I have so much good will for the Sublime team that I'm tempted to buy it without even trying it.
I don't think the prices are comparable to other software since this will be a qualitatively different software-using experience.
I think people often underestimate in general how much really good software is worth. Most software I regret paying as much as I did for but I would pay at least $300/year for Sublime and likely more if that's what they charged. Dash is another good example of software I get way more value out of than what I paid.
Re: Show HN: Sublime Merge – A Git client from the makers of Sublime Text
#227Looks great Jon, happy you are expanding the Sublime family. Can I suggest Sublime Terminal as a possible addition? I'd happily pay for a decent terminal experience on Windows and with your cross platform toolkit it looks like you could deliver that. ConEmu et al just don't do it for me.
We detached this subthread from https://news.ycombinator.com/item?id=18030450.
Re: Show HN: Sublime Merge – A Git client from the makers of Sublime Text
#228I use SourceTree almost solely for its "Split View Staging" feature, where a line or hunk can be moved between the two states and the entire bit you're about to commit can be viewed independently of other working copy changes.
Fits my mental model so well, but is apparently considered too complicated for most other git clients such as GitHub Desktop and Tower.
From the animation, Sublime Merge seems to have Staged/Unstaged areas? Will definitely try this out, as SourceTree is otherwise bloated, slow, and missing critical features.
Re: Show HN: Sublime Merge – A Git client from the makers of Sublime Text
#229Looks like magit, without the very good editor integration that makes magit awesome. Seems nice tho.
Presumably as time goes on it will become more and more integrated with Sublime Text, which is arguably a "very good editor". Or is that not what you mean?
Then it would presumably have been a feature of Sublime Text, rather than a standalone application?
Re: Show HN: Sublime Merge – A Git client from the makers of Sublime Text
#230Hi HN - Jon Skinner here, I made Sublime Text and Sublime Merge, alongside the rest of the Sublime HQ programming team - Will, Dylan and Benjamin. Let me know if you have any questions! Edit: there's also the announcement blog post, at https://www.sublimetext.com/blog/articles/sublime-merge
I work a lot with repos with very long line lengths (regularly up to 10k characters) and have to often check and merge multiple changes per line. I really like Git clients that can do one or all of these things: - Block a small threshold of vertical scrolling when scrolling horizontally on a trackpad to stop the current line I‘m tracking wavering up and down as I scroll. - Highlight whether there are further changes…
Sounds like it might be easier to just write a program which inserts line breaks after periods (and one to remove them), so you can edit the books in their typical format and export to "git format" to deal with versioning/branching/etc. Although it sounds like you've been doing this for a while so there's probably some reason this wouldn't work which I don't know.