Brian Masinick
Today, I’m using Doom Emacs, and as noted, recently I’ve been updating
and running an Emacs server daemon, and when I start each individual
Emacs instance, I run /usr/bin/emacsclient -c -a “emacs” $@, where
each file passed to the command is loaded with the $@ argument.
This results in Emacs starting immediately, and since my configuration
contains Doom Emacs, the emacsclient still runs Doom Emacs as usual.
Also, the emacsclient (and emacs daemon server) are features provided
by GNU Emacs; they are not new; they’ve been in use and well tested
for many decades.
Running an emacs server may not be worthwhile for everyone,
but for a person who uses an editor for most of the day, the
benefit of an emacs client and server with Doom Emacs are that you have
both a vi and an emacs capability when this is running, so there is a
choice of a modal or non-modal user interface and a huge variety of tools.
Examples of capabilities include an integrated git project mechanism,
a file and directory server, Email interface, calendar management, virtually
all command and utility services you’re used to, with a way to access
a shell interface if needed without exiting the environment; there’s very
little that’s not included, and what’s not tightly integrated is accessible
via the command interface.
I’ve been using this regularly for a while now, and there are no
negative consequences of this approach, other than the trade-offs
of a few extra messages each time I run my .bashrc and a slight
increase in shell startup time and modest increase in memory consumption.
To me the gains are well worth these costs because my Doom Emacs
setup invokes as rapidly as several of the very small, lean editors,
and I have a lot more functionality with this setup, so it is well
worth it for me personally.
- This reply was modified 1 year ago by Brian Masinick.
--
Brian Masinick
Alternate "Search B":
This search page