𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍

Bing… X… Facebook… Bing… Google…

Not an Ecosia, Searx, Mastodon, Lemmy, or even DuckDuckGo to be seen. Just dreck.

☹️

Doesn’t it steal control flow? More like a break point, except you define where execution continues.

I wonder if it’s a compile error to have multiple conflicting COMEFROM statements, or if it’s random, kind of like Go’s select statement.

How awesome would it be to be able to steal the execution stack from arbitrary code; how much more awesome if it was indeterminate which of multiple conflicting COMEFROM frames received control! And if it included a state closure from the stolen frame?

Now I want this.

Thanks! Downvotes don’t bother me. I was a big KDE fan, a couple of decades ago, and plasma has been exciting to watch; I was just saying that I wish it’d been as far along when I was still interested in DEs.

There are tiling communities, so I don’t feel a deep need to expound on this; it came across my feed only because I browse World occasionally, - in the name of Eris - and I still get curious almost every announcement. And, every time I try it, it looks very pretty, but I find it counter-productive and fussy, and I end up back in herbstluftwm.

You are absolutely right about the script-ability strength of Linux, and I think KDE of pretty scritpt-able, too. It’s just not a core value, like it is in bspwm or herbstluftwm, and that makes all the difference.

Anyhoo, cheers and have a great day!

Man, I want to try this. But ever since I went fill tiling, scripted WM any DE that forces me to use a mouse just annoys me, no matter how pretty it is.

It’s like when you get really comfortable in vim; any other editor feels like you’ve been given a Studebaker.

Bonus if it can edit .sc files, a-la the best spreadsheet editor, sc-im.

C99 is better. Always will be.

Fight me.

Maybe because not every system is Debian, and Plasma has to work on systems that either don’t have /usr/share/i18n/supported or put is somewhere else?

I manage a project that encounters this sort of thing regularly; my biggest problem is terminfo entries. Not all distributions contain all of the same terminfos. It is one of the biggest source of bug reports my project gets. I’ve been considering just embedding all of the terminfos in my project, just so I know they’ll all be there on every system it’s installed.

I don’t know this is Plasma’s reason for including their own list, but it could easily be. It could also be because those are the locales Plasma supports, and it may not support every locale that might be in the distro system list.

You can’t install FireDragon on any other Linux distribution?

That may be what they meant, but that’s not what it says.

Hugo isn’t a server, per se. It’s basically just a template engine. It was originally focused on turning markdown into web pages, with some extra functionality around generating indexes and cross-references that are really what set it apart from just a simple rendering engine. And by now, much of its value is in the huge number of site templates built for Hugo. But what Hugo does is takes some metadata, whatever markdown content you have, and it generates a static web site. You still need a web server pointed at the generated content. You run Hugo on demand to regenerate the site whenever there’s new content (although, there is a “watch” mode, where it’ll watch for changes and regenerate the site in response). It’s a little fancier than that; it doesn’t regenerate content that hasn’t changed. You can have it create whatever output format you want - mine generates both HTML and gmi (Gemini) sites from the same markdown. But that’s it: at its core, it’s a static site template rendering engine.

It is absolutely suitable for creating a portfolio site. Many of the templates are indeed such. And it’s not hard to make your own templates, if you know the front-end technologies.

It depends on how you want to write. If you want to use a web interface, WriteFreely is decent. If you like your text editor, Hugo is fantastic.

:shrug:

It’s trivial to host yourself, and super light on resources. Personally, I don’t use it; for blogging I write markdown and rsync it over to the server where Hugo picks it up and turns it into a blog. Now that I think about it, I should probably go shut my WriteFreely down. I have a few pages on it, but I hate web app interfaces, so I didn’t put much content in it.

Sourcehut is for-profit. You pay them to host your data, to provide public access, to run mailng lists, to run CI build servers… you’re paying for the services. But the source code is OSS; you can download and run your own services, all or just a few. The “paying them to host the software for you” isn’t the issue, right? It’s not that someone is charging for hosting and maintenance (and, ultimately, salaries for the people working on the software), but whether or not the software is free, and whether you can self-host.

I like your point about finding repos. I think it’d behoove all of the bit players to band together to provide one big searchable repo list. Heck, even I, who hates github with a smoldering passion, have enough sense to go there first to search for software; that’s just the nature of a hegemony. The stumbling of the attempt to create a common VCS hosting API (ForgeFed) is lamentable, but getting adoption would have been a uphill battle even without the rumored in-fighting and drama.

I was amazed a terminal could do that

Yeah, that’s fair. It’s your work; you have no moral obligation to share it. Despite what the commies might say.

I open source all of my projects. Most people I encounter are reasonably polite, but of course even my most popular is used by a tiny fraction of the number of Gnome users. In any case, I long ago stopped caring about being beholden to users. Often they’re doing me favors and finding issues I haven’t, and some even provide useful analysis that saves me work. A few provide contributions. But at the end of the day, I do what I do for me, and anyone else who benefits from it provides a small dose of dopamine from being useful.

I regularly fork projects and implement changes I want; I also file PRs, but in the case the upstream author has different opinions about it, requiring work I don’t think it’s necessary, I just let it go and maintain my own fork.

This is not Ideal Open Software Development, with many people contributing to a common goal. It’s fractured and selfish. But the other way, it becomes work, and nobody’s paying me for this, and so I give no fucks.

My mental health improved drastically once I stopped emotionally caring about the opinions of my users. I still care about the technicalities, but only insofar as they affect me or I deem them to be a superior solution. Key to this is not engaging emotionally; if I’m not interested in working on it, I just say so: I have other priorities, but an happy to review and maybe accept PRs.

The part about negotiation is a bit off-track.

On one end, in the kernel, there’s a big array of pixels that is a picture that gets drawn on your monitor (or monitors). On the other end are a bunch of programs that want to draw stuff, like pictures of your friends and web pages. In between is software that decides how the stuff the softwares want to draw get put into the pixel array. This is Wayland; it was written to replace Xorg, which is what did that job for decades prior to Wayland.

If you understand the concepts of Xorg and window managers, Wayland + a compositor = Xorg + a window manager. Wayland abdicated a lot of work to the compositors, making it simpler and easier to maintain (and compositors more complex and harder). But together, they all do basically the same job. If one of the compositors implemented a network protocol, then you could declare equivalency.

A senior dev writes a program to generate her email.

I have actually done this, and for more than just automated responses. It was before ChatGPT, though; now, I’d be surprised if even junior devs aren’t doing it.

I don’t trust it. It looks shifty. Don’t lend it money.

I’m using herbstluftwm and am happiest with it, but spent years on i3, almost a year in bspwm, and a hot minute on sway. All after years of mostly KDE, some Gnome, and a few years (concurrently w/ Linux) on Macs from work.

Any tiling WM over any DE. I’d go back to i3 before choosing either Gnome or KDE. The one exception would be a fully feature-complete NeXTSTEP clone. I’d switch to that in a heartbeat. Not OpenSTEP, not Windowmaker; NS was beautiful, functional, fully integrated in all aspects - like MacOS, but without the dumbed-down idiocracy.