Follwing Prot’s Emacs: commands in popup frames with ‘emacsclient’ made sense for me. Like https://irreal.org/blog/?p=12460, I struggled with doing this but Prot’s approach _just works_™. 2 adjustments tho: full executable path needed for #emacsclient on #MacOS #KeyboardMaestro & the server config needed to change:
(use-package emacs
:ensure nil
:defer 1
:config
(if (and (fboundp 'server-running-p) ... https://somanyhills.com/2024/09/23/follwing-prots-emacs.html

It's time for another WTF APPLE post!

As you would know, I use emacs-groundup in a server-client setup. While launching the first frame works well, I noticed that launching new frames only works when I'm in the same workspace as the first frame.

Is this a known bug ? My google searches were not very useful (but then google searches usually reveal nothing these days ...).

#macos #apple #emacs #emacsclient

@al3x I personally prefer #vim for small modifications in text files of all sorts.

Not because #Emacs would be bad for that task.

The reasons are that I know both environments and my Emacs does all sorts of things during startup.

On my main host, this would hardly be an issue due to #emacsclient.

However, on all other machines (or users), I'd need to have to maintain a ssh-key-chain to transparently use my main Emacs over the network, sometimes multiple hops. That's tedious to me.

#editors

Anyone with some knowledge about #emacs and #emacsclient and the interplay with the daemon here who can help a user of #JabRef ?

https://github.com/JabRef/jabref/issues/10145

Thanks in advance! Any help appreciated. Please boost.
#linux

So I can ssh to a machine, run emacsclient to connect to the running emacs instance there, write changes that I forgot to write earlier, then either copy them to my other machine or commit on the remote machine.

This is great, but is there any other good emacsclient use case?

#emacs #emacsclient

Took me a whole day to consolidate my #emacs configuration to #systemd + #emacsclient setup.

Goal was simplification.

Struggles:
- systemd config mistakes can lead to silent failures
- I will never master shell script quoting
- moving window (frame) management to a window manager completely is not trivial
- emacsclient has hardcoded action for -a flag, which makes using sockets harder

Full config published here:
https://qua.name/mrb/an-org-babel-based-emacs-configuration

#emacsclient -t in the #terminal does not honor any of the theme settings of the server and is unusable. Thanks in advance for any suggestions to improve the situation. I am using #doomemacs