jD91mZM2

I'm afraid I'm not the messiah you're looking for, then. This is not a replacement for subtrees/submodules. But from my limited experience I agree with what you're saying :)

(Note that subtree is a user-contributed script, but it's been made to ship with most git installations)

I'm unfamiliar with that tool, so you tell me! Looks like it though, from what I'm reading, with the exception of keeping the internal configuration in a git-friendly format instead of huge XML.

Not sure I understand the question correctly, but here goes:

My personal bias is to keep using submodules or at least subtrees where possible, mainly because it's builtin and because it's written by smart people. This is mostly for when repositories are pretty big and you don't want to submodule/subtree the entirety. But that's just me.

I hope the maintainer complexity is as low as any other git solution, all the rebasing tools are just using standard git so there should neither be any advantages or disadvantages. The advantage of using this is to not check in everything into one repository (perhaps avoiding accidental modification of unrelated files that could cause merge conflicts).

Thank you for the feedback, I'll update the README

EDIT: Updated

tmux is pretty darn neat for having multiple terminals inside one terminal, and it's tiling instead of floating. Also lets you detach sessions.

It doesn't. Would be an interesting thing to add perhaps, but then I'd need to add some kind of daemon I believe. I also don't want to compete with the existing software as there's no winning over them.

I just click anywhere there's not a window. Didn't wanna add shortcuts as I'd need some way to escape them

I gotta say what I really like about macros are that ( and )s are matched. If you say:

  while ($($cond:tt)*) {

You'll actually match both

  while (true) {

and

  while (5 * (2 + 3)) {

. It counts the parenthesis :D