tig VS emacs-ng

> I would really like it if Magit was a standalone program, rather than an Emacs package, so that I could just switch to a more reasonable editor.

Always curious with folks who request this whether they've tried `tig` (https://jonas.github.io/tig/)?

Not sure what part of Magit you're looking for, but the basic workflow of jumping to changes and interactive staging works just as well to me in `tig` (with Vim) as Magit.

Use tig. This TUI (terminal user interface) is halfway between the GUI and the command line. It basically does the same thing as the previous command, but it’s easier on the eyes while allowing you to stay in the terminal. It will also make it easier to see the diff for a particular commit.

If you want an interactive commit graph, among other features, look at tig https://jonas.github.io/tig/

https://github.com/jonas/tig is one of the first things I install on a new dev machine. It's a really nice UI for staging files or hunks. Since it's just a companion to the git CLI, it feels much more focused than full-blown git GUIs, and doesn't do anything magical.

Related but I use tig, a TUI, a lot to examine the state of my working tree and index and stage/unstage/reset changes piecemeal. It works great.

I'd like to plug [tig](https://github.com/jonas/tig) for those who don't use emacs. I see lazygit recommended here too, but I've been using tig for years now and love it's simplicity.

Try tig

I'm normally a CLI git (and tig) user.

Concurrency, concurrency, concurrency.

And scripting with JS/TypeScript. Kind of like emacs-ng attempted (https://github.com/emacs-ng/emacs-ng/)

Have a look at remacs (an experimental Rust port of emacs, now discontinued) [1] and its successor, emacs-ng (also in Rust) [2]

I haven’t followed closely, but I am sure there are som valuable lessons learned there that would answer your question.

[1] https://github.com/remacs/remacs

[2] https://emacs-ng.github.io/emacs-ng/

This is exactly what emacs-ng does?

https://emacs-ng.github.io/emacs-ng/

> This project should be considered an additive native layer over emacs, bringing features like Deno's Javascript and Async I/O environment, Mozilla's Webrender, and other features in development. emacs-ng's approach is to utilize multiple new development approaches and tools to bring Emacs to the next level. It is maintained by a team that loves Emacs and everything it stands for - being totally introspectable, with a fully customizable and free development environment. We want Emacs to be a editor 40+ years from now that has the flexibility and design to keep up with progressive technology.

I guess it uses webrender instead of electron?