tarsius

10 ms·

31.
by tarsius 8y ago
That particular issue has been fixed a few weeks ago. You should update Magit. Also you should be able to avoid killing Emacs by just pressing C-g a few times if some subprocess takes a long time.
32.
by tarsius 9y ago
That won't be much of a problem anymore once Emacs 26.1 is released. Meanwhile you can use the latest release candidate - those usually are very solid. For more information see https://magit.vc/manual/magit/Ma
33.
by tarsius 9y ago
On macOS it helps to use Emacs 26.1 (unreleased but very solid) or to use a build with a backport of the vfork patch. For more information see https://magit.vc/manual/magit/MacOS-Performance.html . I also plan to m
34.
by tarsius 9y ago
I think Magit could be classified as a TUI [1]. But that still doesn't help explain its benefits to someone who hasn't tried it. For the crowdfunding campaign that I ran earlier this year I wrote a few articles. For those unfamili
35.
by tarsius 9y ago
Indeed I would not have created Magit from scratch. From the campaign description: "I would like to thank [Marius] and the maintainers who came later, for I would not even have known that I needed something like Magit had they not laid
36.
by tarsius 9y ago
The video is indeed... not so great. I would go as far as to say that this might be the Kickstarter campaign with the crappiest video that ever succeeded. But at some point I just had to launch instead of continuing to hope I would eventual
37.
by tarsius 9y ago
Heh - a happy user just posted a new screencast about Magit: http://emacsrocks.com/e17.html . If that is too short or fast for you; a few older and generally longer videos are listed at https://magit.vc/scree
38.
by tarsius 9y ago
https://emacsair.me/2017/09/01/the-magical-git-interface/#st... Magit is a text-based Git user interface that puts an unmatched focus on streamlining workflows. Commands are invoked using short mnemonic
39.
Show HN: Magit, the magical Git interface(emacsair.me)
24 points by tarsius 9y ago|5 comments
40.
by tarsius 9y ago
During the past few months I have seen a lot of blog posts by burned out maintainers of open source software. One complaint was that companies expect to be treated as customers without actually paying anything. My problem is that I am one
41.
by tarsius 9y ago
Magit is definitely different enough from both your conventional GUI and command-line interface to make it hard to immediately see its benefits, which is why I did not only post some commented screenshots [1] (which may fail to impress), bu
42.
by tarsius 9y ago
Ah, didn't know about this. It was a bit frustrating to see 15 attempts by happy Magit users to let HN know about the campaign fail miserably. Especially because a few weeks earlier "Emacs and Magit" [1] easily made it to #1.
43.
by tarsius 9y ago
I intend to make Magit usable from the command-line, so `magit diff ...` would be similar to `git diff ...` except that the output would be "actionable", i.e. you can use `s` to stage, `RET` to visit the file/blob [edit: even
44.
by tarsius 9y ago
(author here) The support I received during the last three weeks has been phenomenal! Thanks again! The only disappointment was that the campaign did not get a lot of press outside the Emacs community, which was a bit frustrating because I
45.
by tarsius 9y ago
I would probably get drawn into more lengthy discussions. It's important to note that when Richard said that Magit should be "part of Emacs", that really meant "part of GNU Elpa and/or GNU Emacs". If Magit is j
46.
by tarsius 9y ago
Just because you did't make an effort to actually look for these things, that doesn't mean that they don't exist: https://magit.vc/manual/magit/Git-Executable.html .
47.
by tarsius 9y ago
> Can you show me an example of such a package? https://github.com/magnars/dash.el > All the Elpa packages are hosted on a Savannah instance. That's the "publishing repository". You have to push th
48.
by tarsius 9y ago
> use it in a commercial product? Nope. FSF won't allow that. The FSF explicitly allows that. > The assignment contract we normally use has a clause that permits you to use your code in proprietary programs [...] Although we beli
49.
by tarsius 9y ago
Most of the packages that are distributed using GNU Elpa (i.e. the non-built-in packages under FSF control) are developed on Github.
50.
by tarsius 9y ago
> MELPA may also contain unlicensed software or otherwise non-free software. Some statistics on that: https://emacsmirror.net/stats/licenses.html .
51.
by tarsius 9y ago
> If it were part of Emacs you'd need to use the FSF's collaboration tools which have a higher barrier of entry, No, we would continue to use Github for the foreseeable future. If a FSF hosted Gitlab/Gitea/... instanc
52.
by tarsius 11y ago
I clicked on "Sign in" which took my to Github, where I confirmed. That took me to https://www.gitcolony.com/?error=not_found . When I explicitly revisit https://www.gitcolony.com , then I am still not s
53.
by tarsius 11y ago
Discussions about v2.1: - What's new in Magit 2.x https://news.ycombinator.com/item?id=9936095 - Using Emacs and Git with Magit 2.1 https://news.ycombinator.com/item?id=9873237 - Magit 2.1.0, first maj
54.
by tarsius 11y ago
Yeah, that's a bit boring. Personally I use the solarized theme, and have invested more time on that, than the default themes. That's also what we use for the screenshots ( http://magit.vc/screenshots ). Another rea
55.
by tarsius 11y ago
I am not very happy about it, but I have just installed a change that forces everybody to opt-in to the new push behavior.
56.
by tarsius 11y ago
Thanks. It's always nice to hear from satisfied users. This is for the benefit of other users (since you have probably already found these resources): - Release notes: https://raw.githubusercontent.com/magit/magit&