donio

> Furthermore, which Wayland only apps might I want to run on my X11 desktop?

A bit late to the thread but this tool is very much something I've been looking for!

I want it not so much for current use cases but as a way of future-proofing my current setup since there is little hope that I will be replace it with Wayland anytime soon. I worry that a time might come when essential libraries and tools like gtk and web browsers might remove X11 support.

I gave the tool a go and it builds easily and quickly and it was able to run what I've thrown at it so far. One of my concerns was selection/clipboard syncing but even that seems to be working as expected.

It's nice that it doesn't even depend on wlroots which can be a bit of a moving target. It only uses the X11 libs and libwayland-server so I think it should be fairly future proof.

Overall I think this is a much better solution than cage which was the best option I'd found previously.

That's a projection for the rest of the year and probably still way optimistic. It's quite possible that the current trend is for a much smaller number.

I was eyeing the Poqet PC in the late 90s when remaining stock was being sold off at a good price. I wanted to use it as a mobile dial-up terminal and to run Nethack (not sure if it actually had enough RAM and storage for that). Never got around picking one up in the end. Later on my pocket terminal dreams came true thanks to the Nokia 9300, Treo 650 and eventually Android devices using various ssh clients on each.

https://en.wikipedia.org/wiki/Poqet_PC

https://www.bmason.com/PoqetPC/

Besides the limitations others have mentioned users should be aware that since ydotool works by writing events directly into /dev/uinput the input will go to whatever happens to be focused at the moment. It will happily type your secrets into a chat window if you move the mouse at the wrong time.

There is no way to do the equivalent of xdotool type --window 0x600005 "my important input"

I couldn't find an explanation but my guess is that it probably had some edge case failures (like corrupt files after an abort) or it didn't invalidate the cache when autoconf or environment changes affected the test results.

I used to have a wrapper that tried to use a shared config.cache across all projects but I stopped using it around the same time. I can't remember my personal reasons either but must have been something like the above.

I could have sworn that config.cache used to be on by default. And indeed it was until autoconf-2.50 which was released in 2001.

5.6.1 is masked specifically.

Also, https://mastodon.social/@mgorny@treehouse.systems/1121802382... from a Gentoo dev mentions that Gentoo doesn't use the patch that results in sshd getting linked against liblzma.

As far as I know this is not an official communication channel so don't take it as such.

I always cover such tools when I interview people for SRE-type positions. Not so much about which specific commands the candidate can recall (although it always impresses when somebody teaches me about a new tool) but what's possible, what sort of tools are available and how you use them: that you can capture and analyze network traffic, syscalls, execution profiles and examine OS and hardware state.

For what its worth I've yet to see any spam at all in my Mastodon feeds (regular user for about a year, accounts on multiple instances). Much respect to the admins for staying on top of it.

That's a nice way of putting it. When exploring a new codebase for the first time it can be very helpful to have main.go give you a high level idea about the overall structure of the program.

RSS of course. I don't care what platform you use just make sure there is an RSS feed.

Starting with the Spectrum to be precise. The ZX-81 version didn't have that yet.

Regarding the quality of posts in general the problem is not what gets posted, there is a ton of junk in the "new" queue and most of it never makes it to the front page. It's what gets upvoted.

And comparing sizes of areas in general. There is a small card game called Illusion that is built around that idea.

https://boardgamegeek.com/boardgame/244995/illusion

Tornado VPS (used to be prgmr.com) is another one: https://tornadovps.com/order/main/packages/xen/ For $5 you get 1.25 GiB RAM and 15 GiB SSD.

Started using them for almost 15 years ago when running an SMTP server on home-tier internet connections became less feasible.

For everyone else it indicates that Epic is willing to change the terms on you when it suits them.

You can also use Emacs and fennel-mode and then M-x fennel-repl to get a live repl from your Emacs session and then use lisp-eval-last-sexp, doc lookup and other Lisp conveniences.

https://gitlab.com/alexjgriffith/min-love2d-fennel shows a basic setup that enables the repl too.

Not the parent but there are several high quality native (meaning no CGO) Lua implementations for Go and it's a great choice if you want an embedded scripting language:

https://github.com/yuin/gopher-lua

https://github.com/Shopify/go-lua

Unless you specifically need a JVM either of these will be a much more practical and mature choice for embedded scripting.

Alternatively if you prefer JS then Otto is a good choice: https://github.com/robertkrimen/otto

For Emacs users elpher.el is a good option. There are also some additional packages to help with authoring .gmi files either locally or over Titan.

https://thelambdalab.xyz/elpher/

https://git.carcosa.net/jmcbray/gemini.el

https://alexschroeder.ch/cgit/gemini-write/tree/README.md

You can find these in MELPA too.

I used both of these. My WM journey so far:

- olwm/olvwm: virtual desktops and the 19" SPARCStation 2 monitor was absolutely amazing at the time

- fvwm, fvwm2

- sawmill/sawfish was my intro to programmable WMs. It was great until Gnome gobbled it up as its default WM eventually ruining it

- GWM I believe is actually older than then all of the above but I haven't discovered it until I was looking for an alternative for sawfish

- StumpWM was my introduction to tiling WMs and having a proper REPL to allow modifying it live. I don't think that GWM had a REPL but I might be wrong

- EXWM is where I've been for quite a while now. Folding X window management into Emacs buffer management was just as amazing as olvwm was back in the day.

Regarding Sawfish I know that development continued after the Gnome adventure and I could have stuck with it but "Gnome ruined it" is how I perceived it at the time. I can't remember what the specific issues were that made me look for alternatives.

The parent is just being ridiculous, Emacs of course has undo, auto-save and version control. And unlike in certain modal editors it's pretty hard to do any real damage without touching Control or Meta.

I've been using EXWM since 2016 and this hasn't been a problem for me. Emacs doesn't just magically break on its own. And even if I managed to break my config without noticing it the fix is just a git revert away.

I used StumpWM for many years before EXWM and I don't see how the config situation is any different.

Emacs can handle JPEG XL files as long as you build it with ImageMagick enabled and ImageMagick is built with JPEG XL support.

You can try evaluating (imagemagick-types) to see if it's enabled. If it fails with "void-function" that means that your Emacs was not built with ImageMagick enabled. If it returns a list of file types but the list doesn't contain "JXL" then your libMagick might be too old or not compiled with JPEG XL support.

The estimate in the PEP is that it will be 5-8% slower. Having to use more granular locks and atomic operations has a cost.

https://peps.python.org/pep-0703/#performance

Some comp.* groups get reasonable traffic even today although naturally it's mostly the same regulars. And I know of at least a couple of alt.* and rec.* groups that are worth checking on occasion. And there are some others that are kept alive through google groups traffic.

And then there is GMANE.

We also had prc-tools, a free GCC based toolchain. I used it to build a tweaked version of pssh and some other stuff. It was a lot more straightforward than modern Android or iOS development.

https://prc-tools.sourceforge.net/

Some will choose to federate with it (if it's an option), some won't. Just as they do with other instances. That's the beauty of it. Fragmentation is not a bug, it's a feature.

The votes and comments are local to the Endless instance, not forwarded or federated anywhere, correct? So for example if I run a personal one I'd only ever see my own voting history?

To ask the obvious question: Why use this over my favorite RSS reader?

That's what I meant by "no catch-all choices yet". There is no reason Google or Apple couldn't get in the game if they choose to. Supposedly Facebook is making a go at it for whatever that's worth.

I offered the email analogy because that helped me to wrap my head around it when I was starting out.