I have one that I bought in 2013. Has fallen to the floor countless times, still works like day 1.

It is a killer combo!

I’m happily running an Intel NUC as TV computer since 2013, and it’s awesome for exactly the reasons you state. I invested in it when I realized how fully crap the “smart” features of my Samsung TV are. The ultimate controller for it is a combo keyboard and touchpad, I have the Logitech K400r.

The NUC is starting to show it’s age now with its 4th gen i5, and I’m in the process of replacing it with a mini PC with an Intel N100.

It would make sense that a code editor could use a more limited subset of text rendering that could be more optimized.

Perhaps a bit surprisingly, Microsoft actually has pretty good documentation on OpenType. Here’s info on what shaping applies to “standard” scripts:

https://learn.microsoft.com/en-us/typography/script-development/standard

And here’s the landing page for the latest OpenType spec:

https://learn.microsoft.com/en-us/typography/opentype/spec/

Specifically for ligatures, you’re looking for the liga feature which is specified in the font’s GSUB table.

deleted by creator

HarfBuzz does opentype shaping, that is, transforming strings of unicode characters to lists of glyphs with positioning. The significance of this can be hard to understand for someone used to the latin script, as that needs very little shaping - kerning is often the only thing that’s absolutely necessary.

But in complex scripts, most notably the Indic, there’s a lot going on. Unicode characters can merge into one glyph under circumstances, or one character can split into several, and relative positioning in both the x and y axis is imperative.

A reason that OpenType shaping is complex is that part of the rules for what to do will be found in the font, and part will need to be hard-coded in the code implementing it.

If you’re going to roll your own text renderer, you’ll have to care about the following areas:

• Rasterization/rendering to bitmaps, including hinting (notoriously difficult, old-style TrueType hinting instructions are bytecode, so you’ll be writing a tiny VM for this)
• Shaping (Kerning at a minimum, full OpenType shaping for international support)
• BiDi (for full international support, primarily Hebrew and Perso-Arabic)
• A caching system for rendered text glyphs and shaped text runa, as it will be too slow to perform this each time you want to render some text

Let’s just say that I do not recommend going this route unless you’re prepared to spend a lot of time on it.

Y’know, you can turn off auto correction. It’s the first thing I do with any keyboard on any smartphone.

Bon appetite!

Hey man, there’s worse things to be than point of sales!

What kind of socks do you need for Linux Mint? Are any mint green ok?

I think you can even make it a button in the title bar, like the minimize button. Or you should be able to bind a keyboard shortcut to it too.

F or C?

Interesting use case. Sometimes you can find romanizations on lyricstranslate, but this is kinda hit and miss.

Long time since I heard about anyone using CVS. I stopped using it 18 years ago when I discovered how much easier branches were to handle in SVN.

Ah, I might try this 😂 my current strategy is to install and run xneko on coworkers’ computers when they forget to lock their screen, so they will have a cat running after their mouse pointer.

I am the girl! Hmm, but maybe I’ll bring another one too? 🤔

You do you, but I think it’s rarely worth it having the absolutely newest version of something. The Debian version of a package may be older, but often has the advantage of being well-tested. And the Debian version of ncdu is all I’ve ever used and it has worked well.

uniget, huh? That’s not a package manager I’ve ever heard of before.

+1 for zram and earlyoom!

You can use baobab or ncdu to try to figure out what’s filling it up.