From: zimoun <zimon.toutoune@gmail.com>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: Erlang + Emacs profile
Date: Tue, 30 Jun 2020 00:08:40 +0200 [thread overview]
Message-ID: <86eepxbk47.fsf@gmail.com> (raw)
In-Reply-To: <b63704b0-8c9e-0766-f702-bd283c701744@posteo.de>
On Mon, 29 Jun 2020 at 23:12, Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> wrote:
> I'm only trying to understand how it would work with 2 Emacs, one in the
> main profile and one in another profile, which can be created from
> manifest. What I would like to achieve is, that I can do some literate
> programming in org-mode, while following along an online course about
> Erlang. In the past I had some pretty good experience with that approach
> to understanding some code and making sure I also write down what I
> understand, so that later on, I can go back and read again. I am not
> asking, whether this is a good or typical approach to any Erlang
> development.
Having 2 Emacs instances, one in your default profile and one in your
Erlang dev profile does not mean you need complicated init.el file. As
I wrote you earlier, you can use 'with-eval-after-load' and everything
will be fine, even using only one ~/.emacs.d.
> Thanks Simon, it helps!
Welcome! Feel free to ask. :-)
All the best,
simon
next prev parent reply other threads:[~2020-06-29 22:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 22:49 Erlang + Emacs profile Zelphir Kaltstahl
2020-06-24 20:29 ` Maxim Cournoyer
2020-06-25 19:25 ` Zelphir Kaltstahl
2020-06-28 4:41 ` Maxim Cournoyer
2020-06-29 8:50 ` zimoun
2020-06-29 19:37 ` Zelphir Kaltstahl
2020-06-29 20:24 ` Ricardo Wurmus
2020-06-29 20:37 ` Zelphir Kaltstahl
2020-06-29 20:49 ` zimoun
2020-06-29 21:12 ` Zelphir Kaltstahl
2020-06-29 22:08 ` zimoun [this message]
2020-06-29 20:26 ` Zelphir Kaltstahl
2020-06-30 18:34 ` Zelphir Kaltstahl
2020-06-30 18:41 ` Zelphir Kaltstahl
2020-07-06 3:50 ` Maxim Cournoyer
2020-07-07 10:23 ` Zelphir Kaltstahl
2020-07-07 15:55 ` Maxim Cournoyer
2020-07-16 21:34 ` Zelphir Kaltstahl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86eepxbk47.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=zelphirkaltstahl@posteo.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).