"emacs". It is called "emacs"

This happens with iOS autocorrect → https://en.wikipedia.org/wiki/EMac

"Wouldn't it make life easier for us at Apple if we added all of our product name capitalizations like iMac, iPod, etc. into the autocorrect dictionary? Marketing would probably love it too." -Someone at Apple, probably, circa 2006

And here we are.

Its page calls it Emacs: https://www.gnu.org/software/emacs/

X macros can do tons of stuff C++ can't. And if you stick with C, you avoid mountains of C++ problems, even with all the stuff you're talking about.

I love using x macros with c++ to create static types and hooks to disambiguate from basic types. This is more applicable to final executables than libraries - I would never provide anyone with an API based on the mess it creates, but it allows application code to be strongly checked and makes it really easy to add whole classes of assertions to debug builds.

I never said X macros are bad on their own. With C++ you can code exactly as you would in C, but you don't have to manually implement C++ features when there's a need. C++ doesn't have any more problems than C, it's programmers who abuse language features that creates problems.

Or you can, you know, just run Debian.

i was going to just comment "but systemd" but i just found out debian ostensibly supports uninstalling it and installing openRC instead and that makes me like debian more. I use debian for generic VMs, prod VMs are 50/50 gentoo and ubuntu. I've been messing with Devuan too as my primary linux VM on my desktop PC. At one point i had it booting to fully logged in in around 8 seconds (after the bootloader selection thing.) unfortunately i broke that feature so now it takes like 40 seconds. But it is also openRC (there's a pattern here)

Also Yocto supports systemd. I’m using it in my build.

If only one could open the back and replace the battery, the thing that has been known to everybody to wear out while the rest of the device is perfectly functional. One could only dream of such advanced technology. Maybe in 10 years.

You can. Or at least Apple can (for which they’ll charge you $80 or so). Sure, you can’t “hot swap” during the day, but if you like the size, it seems well worth the expense to get a new battery installed.

I know you're trying to make a point or something, but Apple or an independent service center will do just that for not much more than the price of the battery.

Lol, indeed! That was a given with the Nokia.

capitalism breeds innovation!

Yeah. This isn't "raw html", as I understand it.

Yes. It really should be "make" and "make-noguile", but we have what we have. In practice, you actually want the "remake" package. This is a fork of "make" that's a drop-in replacement (since it is the same code), has guile enabled AND contains an interactive debugger.

I wish rmake was in the standard codebase for most distros. It’s absurdly helpful.

Did you try reading the manual?

Can't find it on youtube, link?

sarcasm?

Indeed. Should delete but it's too late.

Certainly not! That would be a faux pas.

Make is a power tool and power tools require effort to fully understand and master (though the base case in Make is surprisingly simple). It also has great documentation (which is something newer generations either don't appreciate or don't care about).

Web browser is 10 times more powerful tool than Make.

And if you want to use it as a build tool, you're going to have to crack open some books.

That's great. Thanks for pointing it out.

Delighted! :-) Glad someone found it a help

GNU Make now has a debugger (`apt install remake`) that eases your first pain point a lot

Even then the problem with doing complicated stuff in Make is that it's very hard to reproduce the environment that triggered the bug in the first place.

I came to the conclusion that you need to treat all of the build system as a linear process, which in Make would mean for example not using "=" at all except to define functions, only use ":=". With this kind of discipline I never really needed a debugger, but really Make is not the right language to write complex logic.

Personally I am a fan of (and contributor to) Meson. It's not perfect but it strikes a good balance between what is in the basic package and what you can do in your build script, and by keeping the build phases separate it really helps with keeping things understandable. The lack of functions can be annoying (and in general I wish it could use Starlark as the language), but it doesn't hurt if you follow the same principle and treat the build script as a data flow process, with each phase producing data structures for the next one. So I think it's generally a good principle to follow.

emacs. Worked great for decades and works great today. Learn it.