github-alphapapa

I will rate your setup a 9/10 if you include prism.el. Why? ...Why not?

You know the discussion's gone off the rails when LWN picks it up. I've been biting my tongue at times while reading it (and now glad that I kept silent...but then, look at me now).

I can't fathom the objections to using cl-lib, especially since something as basic as the built-in debugger already uses it. Elisp is a very pleasant language to work in, but without cl-lib it would be missing basic functionality.

It boggles my mind to see how some people seem to want to write Lisp as if it were C. As an experienced CL hacker I've seen often asks, "Is that the level of abstraction you want to be working at?" These forms from CL allow working at higher levels, treating the lower levels as solved problems that need not be re-engineered at each invocation. They don't increase the cognitive burden--they significantly reduce it, especially when it comes to reading others' code. By using those standard solutions, we stand on the shoulders of giants.

And pcase is, as far as I'm concerned, a masterpiece of programming, a tool I sorely miss when working in any other environment. I really hate to see this incredibly useful contribution of Stefan Monnier's disparaged, especially when much of the criticism merely comes from unfamiliarity and NIHism. (The use of backquote patterns with unquoting to destructure patterns, the same way they're used to construct the same values, is brilliant and naturally Lispy. And the extensibility and modularity of pcase is excellent--compare to, e.g. cl-loop's implementation (another macro I like to use, but it's not easily extended).)

Some of the worst has been to see the disingenuous argumentation presented in these threads on emacs-devel. I've seen a lot of hypocrisy and insulting, passive-aggressive attitudes, blaming one person for what the other is himself doing. It wasn't but a few weeks ago that I noted in another thread how off-putting the discussions can seem to newcomers, only to be told that such impressions are incorrect and invalid--and now to see such awful behavior between people who have effectively been colleagues for years. Is this how we will keep Emacs alive for another 40 years--by artificially holding back the language and viciously attacking those who object?

I think the fundamental question is, is all this worth it? Of all the things to spend the very limited programmer time available, to spend it on rewriting working code to use more awkward and verbose constructs because ideas from Common Lisp have cooties? (Forgive me, but that seems to be what it boils down to.) It's disappointing.

Thanks. A screenshot would be helpful, too. :)

Hm, yeah, imagine some kind of service that takes a question from a user and posts it on Reddit, then feeds the answers into its own ML model and gives something back to the user (with a significant delay, obviously, so maybe more for training purposes).

There was a post here within the past couple of months that, when I looked at its account history, seemed to be obviously some kind of bot, but its writing was coherent enough to seem authentic in isolation.

Seems like a dark time for the Web is coming. :/

It does look nice!

I've no objection to writing another static site generator for Emacs/Org. But the name "One" is so overused. Seems like every company has "Foo ONE" and "Bar ONE". Up til now, Emacs hadn't fallen into that trap... ;)

Anyway, thanks for sharing your work.

I've written about this on my blog too, where you can see the [unsurprising] results of the analysis!

Of course everyone loves to hate on Wesley, but let's face it, he'd probably be the Emacs geek who was constantly talking about this new thing he just did in Emacs, and everyone would be tired of hearing about it. :)

Please read that issue and post a reply to it with the version of Emacs you're using and the backtrace. And please test the branch in the comment that may fix the problem. As you can see, it's been several months since anyone provided feedback, so the fix may already be available, but it needs user confirmation.

Yes, but all those parts that I don't use have cooties! ;)

This sounds very useful. Can it or its functionality be upstreamed?

https://github.com/alphapapa/burly.el: Expressly designed to solve this problem. Use with tab-bar-mode and burly-tabs-mode.

See also: https://github.com/alphapapa/bufler.el with bufler-workspace commands.

Is it just me or have there been a lot of posts lately from accounts with overall negative comment karma.