From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: Re: JIT Emacs parallel world
Date: Sat, 20 Oct 2018 12:04:18 +0200 [thread overview]
Message-ID: <861s8laq8t.fsf@zoho.com> (raw)
In-Reply-To: b3bd878deb50b328ecb6770a47af7200.squirrel@cloud103.planethippo.com
Phillip Lord wrote:
> First, move your stuff from Emacs-24 to
> Emacs-26 -- either one you build or
> a pre-compiled version.
OK, but this implies the same problem, only
Emacs-27 JIT is replaced by Emacs-26. I'm happy
to download and build Emacs-26 from Git but,
again, how do I give it its own .emacs file and
.emacs.d directory so not to interfere with my
repository Emacs-24?
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2018-10-20 10:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 15:18 JIT Emacs parallel world Emanuel Berg
2018-10-20 9:51 ` Phillip Lord
2018-10-20 10:04 ` Emanuel Berg [this message]
2018-10-20 15:26 ` Phillip Lord
2018-10-20 15:50 ` Emanuel Berg
2018-10-24 18:07 ` Emanuel Berg
2018-10-25 10:18 ` Richard Melville
2018-10-25 13:32 ` Emanuel Berg
2018-10-25 19:25 ` Tomas Nordin
2018-10-26 6:04 ` Andreas Röhler
2018-10-26 10:55 ` Emanuel Berg
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=861s8laq8t.fsf@zoho.com \
--to=moasen@zoho.com \
--cc=help-gnu-emacs@gnu.org \
/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).