#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.
@erik it's one of those things -- I've been undoing in emacs since the dawn of time, but didn't know until last year that if I select an area it is localized!
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.
@publicvoit I use exwm, so it's all emacs with some Firefox, generally. Occasionally there's gimp or inkscape, but 95% of my work is in emacs and orgmode.
@publicvoit understood. Except, emacs IS my OS...
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
@publicvoit Ah! Thanks for the tip! I realized I can do it in raw #emacs, without consulting the unicode table, with `set-input-method` `Tex` `` ` a `` For one-offs, though, the unicode table is simpler
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
@veer66 as in, use magit to delete files off the disk? Yeah; I think magit "k" removes them from tracking, magit "K" actually deletes the files.
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
@souldessin how much time did it take to install/setup?
#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
@Crell I did look at yours, but Stack Overflow errors have taught me the hard way that PHP has changed a lot recently. Isn't much of PHP different since you wrote the book?
I'm looking for recent books or up-to-date text on #FunctionalProgramming with PHP. #PHP is changing rapidly and all the books I see are nearly a decade old. Any good recommendations? #FP
I had a bash file that was suddenly failing. After TOO LONG debugging, I found that one of the included functions had been broken so it ended with `fi}` instead of `fi\n}` so a linebreak had been removed. As a result the cron job that depended on that script was failing. #BeautifulBash
Full Stack Clojure web app engineer