So it works well with M-|, but not so well with M-f, for example.
My understanding was that it was used for running x86_64 containers within a arm64 linux VM, because it could provide hardware accelerated emulation for the linux binaries.
My tips:
- Use Alfred. Game changer. It's an immediate improvement on spotlight search, you can run commands with three keystrokes (rather than opening a terminal, just command + space, then > <cmd>), it gives clipboard history and fast append (lets you press command + c twice fast to append to clipboard, and opt + command + c to search clipboard history), and lets you make 'workflows' to make frequent tasks extremely streamlined (I use one to open LLM prompts in five LLMs, so I press command + space 'llm <prompt>' and 5 browser tabs open with the same prompt in grok, claude, chatgpt, perplexity, and (local) deepseek.
- Itsycal: an 'install and forget' calendar for your menu bar (it also uses vim keybindings to move around the calendar which is a fun yet practical easter egg)
- There's still no good window manager for macOS. Rectangle is as close as it gets, but it's not good IMO because it only works on non full size windows. (the solution is just get ninja-like with three finger swipe, and endure using the mouse/trackpad more than you'd prefer)
- Vivid for double the screen brightness
So I've embraced overlapping windows. I strategically place them so that the import parts are visible. For example, my IDE is full screen, but the browser is only 70% with and height or so (so that the left 30% and the bottom 30% of the IDE are visible, which conveniently lets me peek into the log of the currently running program.
I have a Hammerspoon configuration that conjures up a modal window on a keypress, and then additional keypresses move the current window to a predefined position and size, e.g. m to maximize and p for the top right corner (70% width and 70% height).
I also have some keybindings in that modal window to jump to an app, e.g. w for the browser, i for the IDE, t for the email client, space for the terminal.
I very very rarely manually move a window around, one of the preset positions/sizes usually works for me.
Depends on your workflow. I looked at the projects GitHub and I'm confused where the lazy part comes from. The UX seems more complex than just plain git which is much simpler for me. But I rarely do anything other than checkout, add, commit and rebase. And most of them are aliased co for checkout, ci for commit, etc and the rest are tab completed. Starting a TUI and navigating menus would be a waste of time for me.
It seems with the git command line the way to do it is to switch to main then pull then switch back to my feature branch then rebase.
With lazygit i hit f on the main branch which pulls its changes then i can rebase (r) right away.
I also like to review the diff of each file before staging it. I get a nice list of changed files, i can select one and see the diff in it, then I can stage it.
In my opinion and from my POV, Elisp is completely fine - no need to amend or replace it. The last thing I'd like is to mix yet another language into my config (already have to call out to shell and AppleScript).
Now I don't know how annoying Elisp is for package authors, or maybe there's a Guile/Scheme library somewhere out there that Emacs could desperately use.
The problems are IMHO elsewhere, and the main one is that Emacs feels antiquated next to literally any text editor conceived in the past 30+ years. The defaults are awful - most of my config is just fixing papercuts, like adding support for light/dark mode, finding a reasonable font and applying text size consistently, locating the correct LSP executable, or following platform conventions for copy/paste (all across Linux, OpenBSD, and macOS).
I would really like it if Magit was a standalone program, rather than an Emacs package, so that I could just switch to a more reasonable editor.
E.g. I keep wondering whether the split between people who can't live without debuggers vs people who rarely use debuggers is actually people who use IDEs versus people who don't.
But I find that if I have to step around more than a handful of times to find the issue then I forget what happened five steps ago. So I teach for print debugging quite often.
Just an honest opinion of someone who didn’t have skin in the game. Not sure if it helps.