#emacsclient — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #emacsclient, aggregated by home.social.
-
#Emacsclient now launches just fine without me having to stop and restart the service. I changed... nothing.
I hate when this happens. It means it can change back without warning unless I can find out what caused it in the first place.
-
#Emacsclient now launches just fine without me having to stop and restart the service. I changed... nothing.
I hate when this happens. It means it can change back without warning unless I can find out what caused it in the first place.
-
#Emacsclient now launches just fine without me having to stop and restart the service. I changed... nothing.
I hate when this happens. It means it can change back without warning unless I can find out what caused it in the first place.
-
#Emacsclient now launches just fine without me having to stop and restart the service. I changed... nothing.
I hate when this happens. It means it can change back without warning unless I can find out what caused it in the first place.
-
(not so much) fun with Elisp. I try to tell Emacs to avoid a certain frame when opening a file via emacsclient. Tweak display-buffer-alist, no? That non-datastructure of lists of cons cells of lists of cons cells. It took me an hour to get the structure right, only to find out that it works for opening files from within Emacs, but server-mode couldn't be bothered.
Because server-mode does not use display-buffer-alist. Instead it uses server-window. 🤦♀️ 🤯
-
(not so much) fun with Elisp. I try to tell Emacs to avoid a certain frame when opening a file via emacsclient. Tweak display-buffer-alist, no? That non-datastructure of lists of cons cells of lists of cons cells. It took me an hour to get the structure right, only to find out that it works for opening files from within Emacs, but server-mode couldn't be bothered.
Because server-mode does not use display-buffer-alist. Instead it uses server-window. 🤦♀️ 🤯
-
Who needs #sytemd's services when you can open a shell using #emacsclient and #emacs --daemon?
-
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 ...).
-
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 ...).
-
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 ...).
-
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 ...).
-
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 ...).
-
@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.
-
@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.
-
@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.
-
@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.
-
@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.
-
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 -
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 -
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 -
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 -
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 -
I've just realised that half of the key bindings I have defined for #StumpWM are invoking #emacsclient to bring up specific #Emacs windows/buffers.
I used to use #exwm but stopped due to the lack of multithreading. The combination of StumpWM and the Emacs server gives me pretty much the same in the end.
-
Please help me find a #console or #terminal email application that supports #imap4 and #carddav and works on a small screen. It would be great if it's an #emacs application or works with #emacsclient.
I'm looking for this in anticipation of #sharpikeebo.
-
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?
-
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?
-
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?
-
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?
-
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?
-
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 harderFull config published here:
https://qua.name/mrb/an-org-babel-based-emacs-configuration