Replies: 17 comments 1 reply
-
Hey @cwlbraa I think this kind of relates to #158. That issue stagnated though. What do you think about the following solution? In addition to The only possible issue I see - there will be no way to configure socket and server, you'll have to use defaults. |
Beta Was this translation helpful? Give feedback.
-
I'd use the simple solution if it existed, so yeah I think it's good. I'd probably hide the full Emacs.app from Alfred and end up with basically the same behavior as the fancy thing I previously described. I'd also be perfectly happy with defaults. |
Beta Was this translation helpful? Give feedback.
-
Currently I use an "application" created via automator that runs The solution you propose seems about the same, having it included with emacs-plus would be very nice |
Beta Was this translation helpful? Give feedback.
-
It would be great to have the |
Beta Was this translation helpful? Give feedback.
-
I'm having trouble finding |
Beta Was this translation helpful? Give feedback.
-
@restfuladi you can't find it because it doesn't exist :) But there is |
Beta Was this translation helpful? Give feedback.
-
Makes sense, thanks. Any ideas on how to integrate that with Spotlight/Alfred? |
Beta Was this translation helpful? Give feedback.
-
@restfuladi Spotlight/Alfred have issues with symlinks, however Raycast works really well! |
Beta Was this translation helpful? Give feedback.
-
If you create an Automator application for emacs client and put it in /Applications, that should work with Spotlight. I recommend full path: |
Beta Was this translation helpful? Give feedback.
-
Piggy-backing on this issue, happy to make another one - when I launch emacsclient from terminal or Alfred, it doesn't switch to the app - the window opens behind other windows, and then I have to manually switch to it. Has anyone a fix for that? |
Beta Was this translation helpful? Give feedback.
-
Hi, I think Emacsclient.app is a fantastic idea. Is this something that will become available in the homebrew installation? I am new to macos (coming from linux), and I have very little experience doing mac-y things. I also observed what @rross101 said. It's a minor inconvenience, but of course, if it can be addressed it's even better. Software architecture of the mac is so, so inefficient. It's like homebrew is creating an OS within an OS, and obviously there are no standards like XDG or how permissions are managed etc. I can't even get my brew-installed hunspell to integrate with emacs-plus. Sorry for the rant, but macos is just such a user unfriendly environment to work in if you are trying to something even remotely technical. |
Beta Was this translation helpful? Give feedback.
-
The idea is to provide this as part of Emacs+ installation. But it's not high on my priority list. So if someone really wants it, contributions are welcome.
Indeed, macOS is slightly (quite?) different in many regards and might be confusing if you come from newer Linux-es. macOS is based on older FreeBSD.
Look, if you need some help, don't hesitate to open a discussion. The problem you describe is not really related to Emacs+, but it's somewhere on the border, so maybe it's fine :) |
Beta Was this translation helpful? Give feedback.
-
@ChauhanT This is what I did:
@rross101 You could use Apple Script for that: function ec() {
emacsclient $@ && osascript -e 'tell application "Emacs" to activate'
} |
Beta Was this translation helpful? Give feedback.
-
I found I had to tweak @citizen428's answer a little bit to get the applescript to work reliably: |
Beta Was this translation helpful? Give feedback.
-
This works for me. Thank you! |
Beta Was this translation helpful? Give feedback.
-
I changed it to following to set Emacs Client as the default text editor: |
Beta Was this translation helpful? Give feedback.
-
I just checked quickly and noticed that these Automator scripts do not launch emacs when the server is not running. Has anyone else encountered this? |
Beta Was this translation helpful? Give feedback.
-
I love that this formula includes a brew service, and for the longest time I was running that service alongside the Emacs.App. I only recently realized that these 2 paths to invoking Emacs are unaware of each other, and the App will not attempt to connect to the daemon started by the brew service.
If this worked, it'd be amazing for startup times and keeping a single persistent Emacs daemon.
Beta Was this translation helpful? Give feedback.
All reactions