🎉

yay!

as customers users it's great to see this level of customer support

Hi, what are the advantages of running emacs in daemon mode?

I use it only on my laptop. I guess that it would make sense if I had a remote machine where I could run the daemon

https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Server.html

Thanks!

as usual, I forgot that emacs has great docs

No problem. I quickly configured it on y machine as well.

Bit annoying on OSX, though.

do you run it as a system service?

[or however it is called]

Yes

But the problem is that now the Emacs thing in my dock is always on. Which I don’t really mind, but you can no longer start Emacs from that icon.

You have to use emacsclient -c in the terminal

But I open most files from there so no biggie really.

i turned off my dock 🙂

I hardly ever click any icons

i prefer to click cmd+space or just cmd when I am on ubuntu and use keyboard to find what i need

actually it works on windows as well

in Start menu

Hrm, just noticed. When I do emacsclient -c file.ext it opens an Emacs instance immediately but it blocks the terminal

when I do emacsclient -c -nw file.ext it opens emacs in the terminal itself.

Anyone experience with that?

emacsclient -n -c file.ext will not block the terminal.

-n, --no-wait		Don't wait for the server to return

-nw will open a new emacs "frame" on the current terminal, in other words it connects to your running emacs

it's like C-x 5 2 except now the other frame is in in a terminal instead of a GUI

-nw actually just means "no window", meaning use terminal

right, what you said

I can't read

🙂

I've used this sometimes when doing remote pairing with tmux/tmate

so we can share a (terminal) emacs, but I can still edit the same buffers with the GUI if some keybinding stuff isn't cooperating in the terminal

I have emacsclient aliased to emacsclient -nc

that's a neat idea for pair programming

I have a shorthand nc for emacsclient -n. I rarely use more than one frame

except when recording screencasts 🙂 then I have one frame with the episode script, and one frame that I record

I tend to use one frame per project (mostly small NodeJS projects)

usually helps me keep them separated in my head, as they tend to have many files with the same name

since we’re on the topic of frames, i have this in my initializer (set-frame-font "Monaco-16" nil t)

but it doesn’t set the font for frames launched with emacsclient -nc, until i eval it, and then it works fine for subsequent frames.

any clues?!

>(set-frame-font FONT &optional KEEP-SIZE FRAMES) > If FRAMES is non-nil, it should be a list of frames to act upon, > or t meaning all existing graphical frames.

It doesn't apply to future frames 🙂

There are ways to set default frame parameters, including font, that apply to all frames

But what I do is this: (set-face-attribute 'default nil :font "SourceCodePro Medium")

malabarba: Thanks. I did read that, but the behavior I see is that it DOES apply to future frames, once eval’ed explicitly.

which has me confused :S

im also using prelude

which might have something to do with it...

Well. Once you eval it, it reapplies to all existing frames again.

Or are you saying that after you eval it it also applies to future frames?

I use

(setq default-frame-alist '((font . "Source Code Pro-13"))

malabarba: yes it applies to future frames.

which has me confused.

I asked the exact same question here a few months back 🙂 https://clojurians-log.clojureverse.org/emacs/2016-04-29.html

> zzamboni 18:13:31 > @plexus: I always use customize-face and choose default, from which most other faces inherit

plexus: thanks, trying that. It generated a giant incantation to custom-set-faces

I’m going to put that in init and see what happens!

You can put something like this in your init

;; Keep emacs customize settings in separate file
(setq custom-file (expand-file-name "emacs-custom.el" user-emacs-directory))
(load custom-file)

that way emacs-custom.el contains everything that's configured through customized. otherwize it adds that to .emacs/init.el which I'm not a fan of

plexus: yes, thats what i do.

👍

plexus: and it works!

w000t.

\o/ all hail to emacs 🎉

plexus: i was in two minds about committing custom.el to source control. but i guess that makes sense.

yeah that's a normal thing to do. I'm still never sure what to configure through customize and what through good old setq and friends