Hexnut @ambihelical@qoto.org

After having used vi-like keybindings for over 30 years, I've decided to try something new and give #emacs #meow a try. The fact that ijkl are there in the default qwerty bindings is a huge plus, and means I can hobble around initially and not completely loose all of my muscle memory (I still use vim occasionally). I am looking forward to jettisoning a ton of evil specific configuration if I can adapt to meow.

The first road-bump I encountered was that the cheat-sheet came up all wonky, so had to spend the first hour or so figuring that out. Turns out I was using whitespace-mode for text files, and that turns on font-lock-mode which messes up the formatting. I think I did that to lazily get whitespace-mode for some text-mode derived modes, so easy fix.

Now that I can cheat, the next road bump are the window management keystrokes under ^W, some of which I've grown accustomed to. Haven't tackled that one yet, and so any ideas are appreciated.

@rustnl I feel quite strongly that ferris would be showing his tightey whiteys from that angle.

@techflails moving around with your fingers on home row is a good reason. Arrow keys are hard to reach. Meow does look interesting tbh. I’d rather keep a few vim keys due to muscle memory if at all possible.

@wilfredh I'm still getting used to it, and can't really say any particular feature stands out in particular, but in general the whole stack of vertico/consult/embark/orderless,etc seems very well designed and modular. None of the components is explicitly dependent on the other pieces, so any of them can be replaced.

I think it's worth it. I switched from few years of ivy/counsel (I used helm before that). There is obviously some awkwardness switching over, finding replacements for things you are used to, key bindings, etc. So I'd allow for that period of adjustment. You won't be able to just drop it in.

I really like how #emacs has been over the last few years sprouting packages that integrate well with existing emacs functionality. This is in contrast with older do-it-all packages like helm, ivy/counsel which in my usage have been replaced with vertico/consult/etc and projectile which has been replaced by project.el.

Case in point, someone I follow recently extolled the use of helm-apropos, but in #vertico, the emacs command describe-symbol is enhanced with vertico's narrowing framework without having to bind to any new functions. It may be not 100% the same as the helm function (I don't know I've not used it), but it does the job well enough in a nice and neatly engineered way.

I really appreciate this burgeoning attention to engineering, orthogonality and separation of concerns. As a software developer myself, I strongly believe this is the way to go.

@galdor@emacs.ch @ddrake

Helm isn't a requirement for this, there are other narrowing history search packages. If you use consult like me, consult-history seems to work, although I haven't gave it a workout yet.

@Natureshadow@floss.social This is the best one I've found: https://aloso.github.io/2021/03/28/module-system.html
Do you think it would have helped?

Noice

@freemo The ban corresponds to a number of years where there were zero deaths. So I guess I am integrating the curve in my mind. But honestly, thinking about it a bit more, it's probably the # incidents (not deaths) AND the use of assault rifles in the incidents which would be the more useful data to show. Showing the total deaths is more about the effectiveness of the planning (for lack of a better term, ugh) more than what guns were used. 1999 was Columbine for example, which is almost 1/2 of that red peak.

@rdaily @freemo looks pretty flat to me until ban overturn. But in any case the data are useless without info on how many of those shootings involved assault weapons that were acquired during the ban.

@jxf

Somewhat Improved Service

Really Quite Bloated Application

Terribly Obscure Tool

@trinsec @meechele7 Agree. But give it a chance. Write an introduction, favorite some hashtags and put hashtags in your posts if you can remember to do that and it makes sense. There's no "algorithm", hashtags are essential, although boosting is also useful.

@deech Interesting. I’ve seen that dynamic from a few poor team members but here in embedded c++ land with good team members I’ve only had good experience with mandatory code reviews. Helps improve code quality and helps educate less experienced team members. Maybe with a less brittle language it might not be as valuable.

@valere Is it any different from the one at https://excalidraw.com/ ?

@dannyman mais bien sûr

@freemo just how to set it up why you set it up that way what are the benefits etc for future reference mainly, nothing in particular—I’m just curious mainly. I wouldn’t be bummed if you didn’t have time to describe it but it sounds like it would be useful for others as well.