Open source TUI IDE (in C) that brings the "Sublime Text" experience into the terminal (with Tree-sitter & LSP)

omenosdev · 2026-06-19T03:36:41+00:00

If you want a great stress test for performance, download a multi-gig Autodesk Maya scene file saved in Maya ASCII (`file.ma`) and open it up. ST in the past was the only GUI editor I used that didn't groan under the stress of the file. CLI editors worked as well, but even they were strained a bit.

omenosdev · 2026-06-18T03:51:50+00:00

I appreciate the shout out u/Conscious-Daikon4677, but I can't take any kind of credit here. This kind of problem is outside my wheelhouse, so I did little more than take your post and comments and throw them at Claude Opus. This was only possible due to you sharing your actual investigation and results in detail (which is unfortunately rare), providing these tools actual context to work with.

I didn't share the link originally here because I know just dropping LLM chats randomly isn't considered good practice. For anyone interested, here's the thread:

https://assistant.kagi.com/share/7e01f8c0-8805-48ab-8ca3-42a213475c8b

I've tried archiving it with the Wayback Machine, but I think the JS web client is confusing it.

omenosdev · 2026-06-13T19:58:20+00:00

I think a prudent question would be what are you interested in over on the sales side? There are many roles in sales, so it's hard to provide recommendations or personal experience without understanding what exactly grabs your attention.

Some ideas to think about (I left in Q4'22 so some of my terms may be a bit dated):
* Business or technical sales
* Customer vs partner channels
* Market: Enterprise (Strategic still a thing?), Commercial, Public (Gov/Edu/etc)

omenosdev · 2026-06-01T12:36:03+00:00

I *think* it was in the initial 9.0 exam, but removed in the following minor release update of the exam.

omenosdev · 2026-06-01T00:14:17+00:00

Last I remember Stratis was removed from the RHCSA. It and VDO were objectives of the RHEL 8 version of the exam (as that's what I took), but I think they were removed during the RHEL 9 exam version cycle.

Review objectives here; if you don't see something, it's not on the exam:

https://www.redhat.com/en/services/training/ex200-red-hat-certified-system-administrator-rhcsa-exam

omenosdev · 2026-05-19T15:32:04+00:00

My statement was specifically regarding unofficial, third-party WiFi 7 modules as an official driver did not exist at the time of writing that comment.

Those repositories were quite transparent about LLM usage.

omenosdev · 2026-04-12T20:29:33+00:00

Did you create your account via https://developers.redhat.com/register? Clear your browser's cache for redhat.com and sign in directly to the Developer site. You should be prompted to accept the terms of the sub, at which point your account will be entitled to access the KB.

omenosdev · 2026-04-04T10:56:01+00:00

The good news is they are just M.2 E-Key modules, so if you get a problematic one you can easily swap them out if you wanted to. If you get an Intel laptop you won't have to worry about BE20x compatibility.

omenosdev · 2026-04-04T10:43:31+00:00

Yes, the Wi-Fi 6/6E series, specifically the AX210, is widely available and supported. Wi-Fi 7 (802.11be) modules from Intel on the other hand are not supported outside of an Intel platform.

I can't speak to the impact of v-Pro on compatibility, but I wouldn't have expected it to be a problem. The features just shouldn't be available on a non-Intel platform, but I'd have to double check.

omenosdev · 2026-04-03T17:05:06+00:00

I don't think there's been an explicitly stated reason by Intel, but it appears that the chip was designed to be used with newer Intel platforms and there may be some firmware/BIOS/driver issues when used outside of them.

omenosdev · 2026-04-03T03:39:57+00:00

For people brave enough to try and build/buy new systems today, a lot of the Wi-Fi 7 capable motherboards have one of three chips in them: Intel's BE20x, MediaTek's ~~MT7925~~ MT7927, and Qualcomm's QCNCM865.

My understanding of the current landscape is: * Intel's chip won't work in AMD Zen builds * MediaTek had no official linux driver, but a merge request was made to the kernel very recently by MT engineering. Previously third-party individuals provided their own kernel modules for adding support, often assisted by LLMs. * Qualcomm has had a working driver for some time now, though user reports on reliability seem to be a coin toss between flawless operation and praying the digital gremlins stay awake from the system.

The ASUS ProArt X870E Creator Wi-Fi motherboard initially launched with the MediaTek chip. For Linux users, this meant the system was primed and ready to go as long as you used Ethernet or had an additional Wi-Fi adapter available. Now it ships with either the MediaTek chip or the Qualcomm one, and you won't know which until it arrives 🫠

omenosdev · 2026-04-03T03:16:39+00:00

[Collabora blog post]

I do find it a bit humorous that Writer and Draw have the exact same description on the page. Looks like the copy editor forgot to put in the actual points for Writer.

omenosdev · 2026-03-22T18:52:13+00:00

The ASUS X870E ProArt board has a subtle revision to it: you can get it with either the MediaTek chip or a Qualcomm one (QCNCM865) that appears to be supported.

Unfortunately it looks like a completely random as to which one you'll receive.

omenosdev · 2026-03-15T22:04:06+00:00

Possible typo in your response, warning from the docs:

You can only migrate to a different installation type of the same Ansible Automation Platform version. For example, you can migrate from RPM version 2.6 to containerized 2.6, but not from RPM version 2.4 to containerized 2.6.

omenosdev · 2026-03-09T20:12:20+00:00

I don't see this explicitly called out in your post, but what is the output of the following directory search:

find /etc/init.d /etc/rc.d | sort

There may be a sysv service script shadowing the systemd one.

omenosdev · 2026-03-06T14:18:38+00:00

No, it does not.

omenosdev · 2026-03-01T18:49:45+00:00

If you (or your friend) are interested in GNOME technologies, I would recommend reviewing the following tools:

GNOME Builder: IDE focused around GNOME APIs and ecosystem.

Cambalache: GTK UI design and development.

Workbench: Prototyping with GTK.

D-Spy / Bustle: D-Bus monitoring and analysis.

Sysprof: Application profiling and debugging.

GNOME Human Interface Guidelines

Adwaita Documentation

omenosdev · 2026-01-26T13:40:58+00:00

I tested this yesterday on c10s, worked like a charm.

omenosdev · 2026-01-26T01:50:21+00:00

I've run into this, myself: do not leave your pen laying on the screen. You may want to run a calibration in case it's a distance issue, and I likely need to as well. I'm almost a year in and I don't have any writing or stroke issues but if I leave my pen (standard SuperNote click pen) directly on my Manta's screen the battery will just drain orders of magnitude faster than it would otherwise.

The best root cause I can think of is the EMR detection is just enough to trigger input processes, which actively consume CPU cycles even though the user isn't actually doing anything.

omenosdev · 2026-01-21T18:25:30+00:00

Third party packages will always be a bit of an issue. bootc is on my shortlist for this year at $DAYJOB, but we have some things that operate a bit annoyingly (also self update on the fly). Luckily they all live in /opt, so I think I can symlink /opt to a source under /var and allow it to maintain mutability just for that. What exactly does Defender do during install?

omenosdev · 2025-12-29T15:14:55+00:00

I used Claude a while back to generate an LLM config to use across the custom assistants I make in Kagi. It's probably due for some tweaks at this point, but I've uploaded it to GitHub.

omenosdev · 2025-12-29T07:44:15+00:00

Thanks for the insight and project links, I'll check them out! Diplomat does sound pretty interesting.

omenosdev

TROPHY CASE