daptaq

I don't know, my impression from a few years ago is that a lot of the worst, most exhausting people from Twitter got persuaded to use Mastodon, ironically on the grounds that it should do better job at moderation. Mix this with people who are in it for the decentralization and those who see decentralization as a means to withstand censorship, and the overall feel was ... not the best.

Perhaps battery-life?

I don't get what that has to do with my point. Arch leans into terminal enthusiasm, so it is natural that by default all they offer is a tty to install the distribution. But as most other distributions prove, this is not necessary.

Yes, and I use terminal emulators too, but I look at it the same way I look at browsers. Sure, there is a lot of useful stuff being made with heavy Javascript dependencies, weird Web frameworks, etc., but this doesn't mean that the technology is good in itself.

I am saying that terminal emulation is bad?

Acme and Emacs give good examples of how a non-terminal shell session can look like. They also make clear how a good CLI application should behave like.

My constant fear with TikTok is not whether or not you can train it, but whether you will realize when it has managed to train you.

The terminal (or rather terminal emulation) is a mistake, people should stop glorifying it. It has no inherent value, beyond being able to run historical software that was bound to a terminal. Most of all one should stop confusing the terminal and the shell, which remains an interesting concept.

I'm considering to buy a Pixel 5a, seems like the last good phone. It seems there are good deals on Ebay.

So the concept of a prepaid sim card doesn't exist?

You can get a new Nokia dumbphone for 60 euros: https://www.nokia.com/phones/de_de/nokia-6310?sku=16POSE01A0.... Up until recently there were even models that only cost 20.

Why would you even what that? I get the opposite (phone without internet), but this has all the downsides for the development of a child without the advantage of a child being able to contact their parents or vice versa?

So something like abduco (https://www.brain-dump.org/projects/abduco/) should do the job too? I think GP's comment was more concerened with the terminal multiplexing, not the ability to detach a session.

I am not too surprised that the confluence point between Plan 9 and Google have little interest in following the GNU way.

I like to see it this way: A shell /wraps/ the kernel. You cannot issue system calls directly, but a program that handles user input generically (and ideally dynamically), can do this for you. A desktop environment, Emacs, and to an increasing degree web browsers are all different "shells".

Is it only on my system, or does https://fonts.google.com/noto/specimen/Noto+Emoji show a mix of colored and black-and-white icons?

> Emojis in source code and program output, eh, not my style but it's harmless.

Only they do not indicate anything critical. Not everyone has emoji-capable fonts installed.

I believe it to have had issues that lead to inconsistencies and unnecessary complications. More details can be read out of my comparison between the package I wrote and use-package: https://www.emacswiki.org/emacs/SetupEl#h5o-20.

Yet in principle I do agree that it would be nice to have the option. The issue is how to explain this to someone who doesn't know anything yet about Emacs. Talking about the advantages or disadvantages of using a configuration macro requires some basic understanding of what the issue even is.

Ok, I might have misread the comment. But to clarify my own position, I it doesn't necessarily have to be the lack of Experience with Elisp, but with the way you use Emacs and how it behaves (managing buffers and windows, how scrolling works, the little differences in how GUI features behave, etc.). To make use of the easy customization interface, and not get frustrated by it, it help to have some basic experience with Emacs. My intention is to provide a guided tour of what someone might want to have in Emacs, before they begin using it. That way they can get common annoyances out of the way before starting, and have less friction when dealing with whatever remains.

> As an alternative solution, you can ask if the user would like to setup their font on start of emacs and invoke `menu-set-font`. But i think this won't work for people who want to run their emacs in console, another problem i see with this solution is, it would prompt every time emacs starts, which would lead to more confusion.

Interesting idea. It might be possible to generate a snippet that will remove itself after the first initialization, but if that doesn't work at least a comment could be inserted.

> if i read it correctly `document.fonts` reads like "get all the fonts used on this web page" rather than "get me all the fonts installed on this computer".

Ok, I see. Another possibility would be to use https://developer.mozilla.org/en-US/docs/Web/API/FontFaceSet to check for the avaliablility fixed set of popular fonts.

I understand your point, but I am not convinced. Nit because I belive in some inherent superiority of some or another set of keybindings, but rather because on the one hand evil isn't a perfect emulation (any somewhat experienced Vim user can always name me a few faults), and on the other the very need for evil-collections to bridge the gap between Emacsy conventions that packages conventionally use and Vims keys (e.g. Dired becomes practically useless if it were to overwritten by Evil keys).

Could you elaborate on what you mean? The intention is not to have a finished configuration that requires no more work, but to provide a template on which further customizations can be made.

Sadly, you are right. Fixed it here: https://git.sr.ht/~pkal/ecg/commit/c3522dfe01e0479d01869bf4e...

I have no experience with Evil or that entire space. I would be interested to look into how the situation can be improved, but then again, I do believe that evil-mode is fundamentally just an emulation layer, and shouldn't be regarded as an equal to the regular keybindings.

I recognize the advantage of tags, but everything else seems superfluous for a personal configuration. For beginners it just one more thing that can go wrong. I have read dozens of supposedly literate configurations on the web, and most of them are just header, begin_src, code, end_src, repeat. There are rare exceptions, but these cannot be generated automatically.

I cannot comment on the differences, all I can say that I chose Eglot because it is more in line with my understanding of an ideomatic Emacs package, and it is available via GNU ELPA.

> You also have not enabled many of the modes that you install which will be a not fun experience for the newbies you are targeting. That is unintentional, I will review the packages I have missed.

> Use-package could actually help a lot in your backend generation code I think (ie because consistent data model). Theoretically yes, but that would require some restructuring in the backend. It is a goal though, at least as an option next to no configuration macro and Setup.

> evil-collection would be a good add as well as quite a few evil quality of life items. Will look into this, I don't use Evil so it is hard for me to judge.

Thanks for noticing the issues, I will fix the issues and add the other features.

> Did you not add use-package because it's not in the repositories you're using, or something else?

Mainly that, but also I am not too fond of use-package. If I add support, it would be with my own package (setup) as an alternative.

> Great choice adding Modus themes!

Well they are bundled in by default.

> * undo-tree. Not sure about this, I have heard people having issues with undo-tree due to the way it is implemented. Vundo seems to be an interesting alternative, but that is Emacs 28+ only.

> * Magit keybind seems redundant as the package itself adds them, and it's swapped. True, but it binds to the C-x prefix which I think is a mistake (especially because it is one automatically).

I wouldn't say so, customize is a useful interface to get an overview of all the options a package or feature might provide, but without any order or structure beyond the group hierarchy.

This seems very unlikely, since CUA mode doesn't work perfectly, and the chance of the C-c prefix being given up for a single command is next to zero.