I spent 30 hours and a sick day debugging an issue I thought was my xorg setup when, in fact, it was a cruel #guix command combined with a bad version of the #LinuxKernel
#CSS media queries are worth the time and effort to remove. Modern responsiveness doesn't require specific pixel values. Why did no one's code sense start tingling a warning that Media Queries were never a good idea? #ResponsiveDesign #DRY
Why does my #emacs crash every couple hours of work? I can be doing whatever, even writing non-code. I can be in Gnome or in EXWM. Today it's occurred after about 2 hours of work, and then again 2.5 hours later. It doesn't seem to matter my window-load or my CPU load; I just hear my fans start whirring, my CPU usage goes way up, and I either freeze or even my cursor becomes sluggish. This didn't happen very often a month ago, back on emacs 28.2. What could be causing it now? Maybe #GarbageCollection?
#guix gc is already a wonder for freeink up space. `guix gc --delete-generations` just freed over 50GB. Now will my exwm stop loading emacs 28.2 when at a prompt I get 29?
My #guix gc freed about 14gb. How about that? #GarbageCollection
Today I learned about #gnuOctave, apparently as an OS alternative to #MatLab. Full disclosure: I've never actually used matlab. Does anyone have experience with Octave? Was it good?
https://wiki.octave.org/Differences_between_Octave_and_Matlab
My life is so much better after I removed #emacs #UndoTree. Things that I just wrote off as failing before, and as freezing my process, just WORK now. For example, it turns out that "elfeed update" causes big buffer changes and that undotree was freezing the thread trying to track those changes. Same story with Telega startup. I had really suspected that my HD was failing; it didn't occur to me that I was getting sabotaged by a global buffer-monitoring plugin.
#emacs I was experiencing freezes of sometimes up to 30 seconds about 3/4 of the the time when I used my muscle memory to hit "undo", which I do as part of my regular "kill-line undo" combo. Something must have changed recently because I started to have show-stopping freezes of my emacs thread when I tried a routine "undo." I finally managed to squeeze a `toggle-debug-on-quit` and, with a bit of patience, got a C-g in during the freeze. The culprit in the resulting stack trace was my global undo-tree mode, which in combination with my other settings must have started failing. I turned it off by removing the line in my init.el and also running `global-undo-tree-mode` to toggle the mode and… far, no more funny freezes on undo. There are occasions when the undo tree is great and useful, but not at the cost of sometimes completely being a show stopper.
The fact that #emacs out-of-the-box includes "undo-in-region" is not only super cool, but also extremely useful. I just copied a bunch of stuff, changed it into org headings, updated the title, then realized that the stuff had multiple lines, so I undid just the heading part and removed the linebreaks before going back to headings -- without undoing the title change.
I need a bunch of historical weather data. After some dead ends, I've found Open-Meteo:
- years of data
- hourly observations
- all the metrics, even weird ones
- downloadable as CSV
- API available
- free for non-commercial use
I'm in total shock. This is the greatest service of all time, and it's been right here all along --> @openmeteo
Will "Live Tweeting" a big event cause issues on a #mastodon instance? I know that cross-posting back in the day between Twitter and Mastodon seemed not good
til the most used web engine is not Webkit or Gecko -- it's Blink. Funny that I have been hearing about the others for years. https://en.wikipedia.org/wiki/Comparison_of_browser_engines
I love this quote. Can't seem to find the original author to give attribution where due:
Vim is immortal in the nokia brick-phone sense. It's got very few dependencies, it'll survive a drop from a ten foot pole and it's cooperative with like thirty year old technology. It's fast and ergonomic and once armageddon comes you'll shell into the flaming wreckage of a datacenter and edit configs with it. Pure embodiment of the strength and certainty of steel.
Emacs, by contrast, is immortal in the shambling fleshbeast sense. Its thousand thralls write beautiful evocations to pull domains you never could have wanted or imagined from its flesh. It grows cancerously to envelop any domain, any need you may want from it. You can tear out its heart and swap it, still-beating, for a new one. It embodies the ultimate desire to survive. It can send email
#Gitlab can be self-hosted. This gets around things like user limits, which are a current blocker. But should we? Pro, cons, alternatives? Dear Internet, please advise
Full Stack Clojure web app engineer