unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Phillip Lord" <phillip.lord@russet.org.uk>
To: help-gnu-emacs@gnu.org
Subject: Re: JIT Emacs parallel world
Date: Sat, 20 Oct 2018 05:51:20 -0400	[thread overview]
Message-ID: <b3bd878deb50b328ecb6770a47af7200.squirrel@cloud103.planethippo.com> (raw)
In-Reply-To: <86a7naart0.fsf@zoho.com>

On Fri, October 19, 2018 11:18 am, Emanuel Berg wrote:
> I think the easiest way to get my gear from
> Emacs 24 to Emacs 27 JIT is to start over and
> bring stuff over one piece at a time, correcting each error/warning as I go
> along.
>
> So the current situation is, I have Emacs 24
> installed from the repos, I have Emacs-w3m installed from the repos, I have
> all my gear in a directory in ~/.emacs.d, which is loaded from ~/.emacs -
> all everyday stuff in other words.
>
> Emacs 27 JIT tho I got from Git and built
> manually - if that is the right word - but I didn't install it. So I have
> it in a directory all to itself.
>
> Now, in order to carry out my plan, how can
> I tell Emacs 27 JIT to look for another init
> file (NOT the one I have for Emacs 24, ~/.emacs), and use another Emacs
> directory (NOT ~/.emacs.d) ?


This is not the right way to do things. Emacs-27 is currently not released
and liable to be unstable. The jit branch is more so. Updating from an old
version (Emacs-24) to an unstable branch is not going to leave you in a
good place to debug any issues.

First, move your stuff from Emacs-24 to Emacs-26 -- either one you build
or a pre-compiled version. If want to try Emacs-27 with the JIT branch, do
so from there; there is a reasonably good change that you will have to
make no configuration changes between 26 and 27 (jit or otherwise).
Install as many packages as you can via package.el. Personally, I modify
`package-user-dir'  so that it includes the version number and
auto-install packages with use-package, but this is probably not
necessary.

Finally, I would use `git worktree` so that you can have both Emacs-27 and
Emacs-27 JIT branch compiled and ready to go. If you are going to live on
an unstable Emacs you may find yourself needing to switch periodically.




  reply	other threads:[~2018-10-20  9:51 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 [this message]
2018-10-20 10:04   ` Emanuel Berg
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=b3bd878deb50b328ecb6770a47af7200.squirrel@cloud103.planethippo.com \
    --to=phillip.lord@russet.org.uk \
    --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).