Toggling Narrowing

Over at the Emacs subreddit, sebhoagie has a short post that some of you may find useful. Sebhoagie really likes narrowing and uses it all the time. Sometimes, though, the narrowed code refers to code outside the narrowed region and he occasionally wants to reference it and then return to the narrowed region.

That’s not a big problem of course. Just widen, search for the referenced code, highlight the original narrowed code, and renarrow. Of course there’s a bit of friction and if you need to do it often it can become a burden.

Sebhoagie has a writeup that explains his solution. The TL;DR is that he wrote a function that narrows to a region but when you widen, it remembers the narrowed region. If you narrow again (using his function) it will renarrow to the previous region and forget the saved region parameters. If you think it through, that does exactly what you want. When you’re finished with the narrowed region you simply widen in the normal way (with widen) and everything is reset.

My solution is to use Artur Malabarba’s narrow-or-widen-dwim that almost always does exactly what I want. Take a look at Malabarba’s post to see how it works. If you’re not using it, you’re definitely working too hard. Still, you may find sebhoagie’s useful. If you have a similar need, his code is a nice companion to Malabarba’s.

Narrowing really can be a superpower as sebhoagie says and it’s worthwhile making its use as easy as possible.

Posted in General | Tagged | Leave a comment

The Apple Decision

By now, everyone knows about Judge Yvonne Gonzalez Rogers’ decision that Apple can no longer refuse to let apps link to payment methods outside of the iOS app system. The idea was that if you ordered anything through an iOS app, Apple would get a percentage of the sale. Everybody but Apple hated the policy.

I’m conflicted on the matter. My inclination is to side with Apple. After all, they built the iOS app platform—without which, by the way, those complaining wouldn’t even exist—and they should get to set the rules. I think it’s a huge stretch to claim that setting those rules is somehow an antitrust issue. Others obviously disagree.

I don’t write iOS apps so my perspective is that of a user. One aspect of that use is the iOS Kindle app. Often, when I finish reading a book, there’s a recommendation for the next book in the series. If I liked the book, I will usually order the next book to read later. It’s not a seamless process. I have to leave the Kindle app, go to the browser, bring up the Amazon site, search for the book, and, finally, order it.

Now, happily, that has changed. The Kindle app now has a button that allows you to go to the book’s Amazon page and order it right from the app. I’m really happy about that but I can’t help thinking that it’s not right. It’s almost as if I’m abetting theft from Apple. As I said, Apple built the platform and others came along and claimed rights to it.

I get that app developers are living on the edge and I do think that Apple can afford to and should let them suggest other payment options. And really, most of us are going to take the easy option and order through the app anyway. Still, it’s Apple’s platform and they should get to set the rules. If you don’t like the rules, build your own platform. If you don’t think that’s possible, ask Steve Jobs or Jeff Besos.

Posted in General | Tagged | Leave a comment

A Small Git Improvement For Elisp Files

James Cherti has a quick tip on configuring Git to provide more meaningful diffs for Elisp files. The problem, he says, is that by default Git diffs simply provide a line-by-line difference with no added context such as what functions are involved. It turns out that it’s pretty easy to provide that context.

The process is pretty simple. First you have to provide a regular expression that recognizes the various def constructs such as defun and defmacro. Then you tell Git to associate that regex with Elisp files. After doing that, you get a bit more context in your Git diffs.

Take a look at Cherti’s post for the details. It’s a small thing but easy to do and it may make your change analysis a bit easier.

Posted in General | Tagged , | Leave a comment

Emacs For Non-Programmers

MarchZealousideal543 over at the Emacs subreddit asks a familiar question: Is it really feasible or even possible for a non-programmer to use Emacs productively? I know I write about this a lot but I find the subject fascinating. MarchZealousideal543 got steered onto Emacs by asking some AI for suggestions and apparently Emacs was the overwhelming recommendation.

There’s nothing very interesting about such questions, of course; the interest is in the comments. There’s the usual ankle biting and nonsense but a lot of the comments are excellent and tell stories of how people from all walks of life—even someone in construction—use Emacs to run their lives, careers, or businesses.

The one thing that many of them say, though, is that you should expect to spend a few weeks getting up to speed with Emacs. Those of us who have been using Emacs for decades and still consider ourselves barely up to speed can only smile. Nevertheless, they all say that the startup time is worth it and that you will soon become proficient.

The other story that came up more than once was how the secretaries at the MIT were introduced to Emacs and given a small write up on how to configure it. Because they didn’t realize they were programming, they soon were soon automating their workflows.

If, like me, you like reading about non-technical people using Emacs, take a look at this reddit post.

Posted in General | Tagged | Leave a comment

Searching The Web With Emacs

If you’re one of those brave folks who doesn’t mind browsing the Web from within Emacs, I just came across a package that may interest you. It’s emacs-websearch a small utility that lets you specify a term, search for it on the web, choose one of the results, and open that page in your Emacs.

That may sound a little complicated but take a look at the animated GIF at the link. It seems like a pretty nice workflow. Right now, it supports Duck Duck Go and Google but looking at the code, it would be easy to add your favorite. You can choose between using the xwidget toolkit and eaf-open-browser to display the Web page.

This is one of those small packages that mainly scratches the author’s itch but can still be useful to the rest of us. Take a look and see if it might work for you.

Posted in General | Tagged | Leave a comment

Accessing Research You Already Paid For

A long standing source of frustration in the research community has been the locking of research papers behind paywalls. It’s easy to see how detrimental this is to the scientific research enterprise. After all, the purpose of publishing papers is to share the research results among the greater scientific community.

For all of my adult life—and probably longer, maybe even forever—the research behind these papers have been paid for by the government. In modern times, that means you and me. So here’s the consequence: we pay for the research but can’t read the results of that research unless we want to pay substantial fees to the publishers of the associated papers.

You can easily see the problem from the publishers point of view. It’s an existential threat. If the papers were made available without charge, why would anyone (or more specifically, any institution) pay thousands of dollars a year for access to the journals? The journals argue that they do provide added value. They perform curation, editing, and perhaps most importantly, peer revue of the papers.

But here’s the thing. Except for some in-house copy editors, they don’t pay anything for those efforts. They’re all considered necessary public service on the part of academics. So all of that “added value” can be and is provided for open access, on-line journals. Really, the only reason that paid, dead tree journals continue to exist is academic tradition. The journals have always played a huge role in tenure and promotion decisions in academia and many can’t imagine any other way of doing business.

Regardless, for research funded by the US National Institutes of Health, at least, the journal monopoly is coming to an end. Effective July 1, 2025, the results of all NIH supported research will be available without charge. This is a slight acceleration of the previous policy that required public availability by December 31, 2025, but it serves as notice that this long standing rip off of the public will no longer be tolerated.

Of course, research not funded by the government—if there is any—is not affected but it’s hard to imagine there’s enough of it to make it worthwhile to keep charging for it. Maybe the journals will find a way to reconfigure their business model or maybe they’ll simply go out of business. Either way, we’ll be better off. These days, it’s easy to publish on line and for those who want curated papers, there are already open access sites providing that service.

Posted in General | Tagged | Leave a comment

🥩 Red Meet Friday: Parenthesis: Get Over It Already

As you almost certainly know, we here at Irreal have little patience for those constantly whining about parentheses in Lisp. They seem to us like little kids complaining to Mom that “it’s not fair”. Apparently, we’re not the only ones. Joe Marshal, who I’ve mentioned before, is an old time Lisper—so old timey that he worked on the firmware for one of the actual Lisp machines—who also doesn’t have a lot of patience for the whining.

He settled on a unique solution. He asked his AI client, Gemini, to write a rant for him. I have to admit, as much as I dismiss the current AI craze as voodoo, the rant was probably better than I could have written. If you, too, are tired of the jejune whimpering from the ignorati, take a look at Marshall’s post for some well earned relief.

Maybe we can enlist an army of these AIs to beat the whiners into submission or at least into complaining about something else. The Illuminati maybe.

Posted in General | Tagged , | Leave a comment

Journelly!

Hooray. Journelly, which I think of as an iOS front end for Emacs’ Org mode, has been officially released. For those of you who have been waiting for an official release to try it out, your time has come.

I’ve been using this app everyday for the last month and even though I was working with a beta, it has been rock solid. I really, really like this app and recommend that everyone try it out. It’s $14.99 but let me assure you that it’s worth every penny.

One of the things that I haven’t mentioned in my posts about it is that there’s seamless syncing of your data. No third party apps or difficult configuration. You simply specify that you want to sync your data to iCloud and it’s instantly available to Org mode on your Mac and the rest of your iOS devices. Exactly what we expect, but seldom get from apps that interface between iOS and Emacs. Ramírez says that exporting to Markdown is on his todo list so even if you aren’t—for some reason—an Org mode user, he’s got you covered.

This is the first app that I’ve bought for a long time but I’m happy to spend the money. Journelly has become an important part of my workflow.

Posted in General | Tagged | Leave a comment

Preventing Minor Modes From Appearing On The Mode Line

The Emacs mode line contains a wealth of information, much of which I depend on daily. Some of that information is what the major mode is and what minor modes are active. Again, that’s often useful information. Still, there are plenty of minor modes that I don’t care about, either because they’re always enabled or because they simply don’t matter to my workflow.

For a long time, the standard way of dealing with that was the diminish command that would prevent a given minor mode from appearing on the mode line. The problem was that it sometimes didn’t work and, at least in my experience, every update of a package would reset the diminish function to off for that mode.

Relief is finally—or at least will be—here. Coming in Emacs 31 is mode-line-collapse-minor-modes. The idea is that you will list in a single variable those minor modes you don’t want to appear on the mode line or, optionally, those you do. By default those modes excluded are represented by a single ... on the mode line. You can click on that to see a list of the hidden modes.

As I’ve said before, I usually have two side-by-side windows in a single Emacs frame. That means that there’s not a lot of room on my mode line so getting rid of less important information is essential to me. Diminish has worked reasonably well for that but I’ll be glad to have a simpler way of handling the problem. Emacs 31 is still sometime away but it’s something to look forward to.

Posted in General | Tagged | Leave a comment

Scrim Released

A couple of weeks ago, I wrote about Charles Choi’s Scrim beta. Scrim is an app that makes the Org Protocol work in macOS. The problem, as Choi explains is that Org Protocol depends on calling emacsclient to deliver the messages to Emacs. Unfortunately, this became impossible when Apple started sandboxing applications for security reasons.

Choi is a huge fan of Org Protocol so he he wrote Scrim to act as a native macOS client for Emacs server. That gets around the sandboxing and allows Org Protocol to work on macOS. Scrim is now available on the on the App store by itself or as a bundle with the related app Captee that allows sharing links from other applications via the share menu.

I’ve tried using Org Protocol before but could never get it to work. Now I understand why. If you too have tried and failed to get Org Protocol working, you can get Scrim and Captee for $7.99. That’s a very reasonable price and since the two apps scratch one of Choi’s itches, it’s very likely that they’ll be maintained on an ongoing basis.

Take a look at Choi’s announcement to see if Scrim might be helpful to you.

Posted in General | Tagged , | Leave a comment