u/cidra_

Note: Lenovo Duet 11" Gen 9 MediaTek Kompanio 838 with 8GB of Ram. Being precise about it since the Duet line has a terrible name scheme

My GF is a primary school teacher and she got a 383€ bonus to spend before the end of august for laptops and tablets.

Laptops are a no-go as there's no real need for it: they're unnecessarily power hungry and the small form factor and efficiency of ARM is preferred, as well as the stylus support. Nice Google integration is also a nice-to-have since she got a Pixel 9.

I can state that the tablets market is terrible: the only choices so far are Android tablets of different manufacturers with different guarantees of software support, a desktop mode that appears to be still in beta and an all-around os that is clearly still mobile-first. The alternative is an Ipad A16, but I'd have to add around 50€ and still would have to buy a pen and keyboard separately.

Then there's the Duet 11 128GB/8GB with Mediatek 838, which is on sale here in Italy for 300€. Seems like a great deal: it is a dead simple OS that is desktop first and yet has the efficency of ARM, no downstream bloat from the manufactures and comes with a a cover and keyboard (the pen sold separately but those 35€ are still in budget). The lack of DRM is not an issue as Netflix is not used there.

The only catch: it is basically declared as a dead OS. Paradoxically it's got guaranteed updates until 2034, which is at least twice as many as your average Android device, but how relevant will Chrome OS, compared to the newest Google Books with Aluminium OS? If it's got to be a big deal software-wise I might consider finding a way to postpone the purchase until their release.

My Onyx Boox is at 0 degrees portrait, but everytime I open KOReader I need to rotate it 180 degrees. Also, when opening a book, sometimes I need to rotate again, for some reason. Doesn't it support auto-rotation?

Hi all,

This is a small package for running commands in a Toolbox container (or similar) while staying in your local buffer.

I've had already discussed about this peeve of mine in the past, and this is the potential solution I've came up with.

It's alpha stage, but the core idea works and should be easy to try out. Would love feedback on the UX and the overall approach. Thank you in advance!

It seems that the only FOSS and stable launcher without app drawer is Bliss Launcher 3, which is apparently only compatible with /e/OS. Has there been any attempt in making this compatible for other ROMs as well?

Just got an email that warmed me that next week's flight got delayed and I'll arrive at Liverpool at 11PM. Can't refund the flight. What's the best way to get to Manchester at 11PM?

I've not seen many anime and my tastes are quite mainstream. This is a list of my favorite animes (Which covers the 80% of what I've watched since I'm quite picky)

1. Mob Psycho 100
2. Frieren: Beyond Journey's End
3. Cowboy Bebop
4. Samurai Champloo
5. Great Teacher Onizuka
6. FMA: Brotherhood
7. One Punch Man S1
8. Neon Genesis Evangelion
9. Death Note
   
Enjoyed watching but not really my genre: Jujutsu Kaisen, Tokyo Ghoul
Special mention, but same as above: JJBA 

I'm drawn to either original/groundbreaking writing (Frieren, Mob Psycho 100), light and easygoing "good vibes" shows (GTO), or emotionally heavy stuff with a god-tier soundtrack (Cowboy Bebop, Samurai Champloo).

Brasero Flatpak crashes, unfortunately

Ho una batteria avviatore d'emergenza della NOCO che pare essere molto robusto e credo dichiari anche di sopportare alte temperature, ma vorrei comunque trovargli una buona sistemazione in macchina per evitare spiacevoli sorprese. Per ora lo tengo conservato nel vano portaoggetti in basso e davanti al sedile del passeggero

I want to accomodate the Smash default settings and NOT use the C-stick for tilt attacks. Here is a 1 minute video of me quickly trying to tilt attack in various directions.

Inputs are really tight, to me it looks that inhumane muscle memory is needed to perform such inputs reliably in a real fast paced match. What's the rationale of such overloaded commands? How can I stay committed to my purpose and get more precise at tilt attacking with the control stick?

Discussione nata per curiosità con un amico, quindi è un puro esercizio teorico e non una situazione reale.

Immaginate di lavorare per un'azienda che vi offre due alternative:

• auto aziendale a uso lavorativo
• utilizzo dell'auto personale con rimborso chilometrico secondo le tabelle ACI.

Senza entrare troppo nei dettagli specifici (modello dell'auto, condizioni contrattuali particolari, ecc.), e premettendo le ipotesi che ritenete più ragionevoli, quale soluzione sarebbe generalmente più conveniente dal punto di vista puramente economico per chi percorre circa 50.000 km all'anno?

Mi interessa soprattutto capire come ragionereste sui costi complessivi (acquisto, svalutazione, manutenzione, carburante, assicurazione, rimborsi, ecc.).

Much of the development these days can happen inside a container thanks to Podman, Toolbx, Distrobox, Apptainer, and the like. Emacs doesn't lack facilities for this: TRAMP exists, but using it for container workflows feels like a category error to me.

TRAMP's semantics are built around accessing remote files, but what I really want is to access local files with a "remote" (but also not really remote) set of binaries. This mismatch causes real friction:

• Files are treated differently. Buffers pointing to the same file are seen as different depending on whether they were opened locally or via TRAMP.
• Paths diverge. Recentf may show the same file with different paths. It is hard to navigate across different projects which use different containers as you would have to modify the TRAMP prefix in C-x C-f
• Subprocesses are all-or-nothing. In a local buffer, everything runs on the host; in a TRAMP buffer, everything runs in the container. There's no middle ground.
  • Tooling must be duplicated. You end up needing git, ripgrep, etc. installed in every container just to get a consistent experience which defeats part of the point of a lightweight container.

What I'd find more natural is opening buffers locally but selectively choosing which commands to execute inside the container: e.g., having M-x compile automatically prefix with toolbox-run -c Fedora, or having Eglot spawn the LSP server inside the container while the file buffer stays local. As far as I can tell, the only way to achieve something like this with M-x compile is through advising, which feels fragile.

Before I go off and reinvent the wheel: does anyone share this peeve and has already put together a setup that works this way? I'd love to hear how you've adapted Emacs to handle the "local files, containerized tooling" pattern.