From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: Re: JIT Emacs parallel world
Date: Fri, 26 Oct 2018 12:55:51 +0200 [thread overview]
Message-ID: <86mur1q8nc.fsf@zoho.com> (raw)
In-Reply-To: 4c1a8858-e366-ccfd-b1b2-d05c2a3960da@easy-emacs.de
Andreas Röhler wrote:
> I'm using .emacs only to dispatch
>
> (cond
> ((string-match "^23" emacs-version)
> (load (expand-file-name "~/.gnu-emacs23-all-cvs"))
> (setq custom-file (expand-file-name "~/.gnu-emacs23-cvs-custom")))
> ((string-match "^24" emacs-version)
> (load (expand-file-name "~/.gnu-emacs24"))
> (setq custom-file (expand-file-name "~/.gnu-emacs24-custom")))
> ((string-match "^25" emacs-version)
> (load (expand-file-name "~/.gnu-emacs25"))
> (setq custom-file (expand-file-name "~/.gnu-emacs25-custom")))
> ((string-match "^26" emacs-version)
> (load (expand-file-name "~/.gnu-emacs25"))
> (setq custom-file (expand-file-name "~/.gnu-emacs25-custom")))
> ((string-match "^27" emacs-version)
> (load (expand-file-name "~/.gnu-emacs25"))
> (setq custom-file (expand-file-name "~/.gnu-emacs25-custom"))
> ))
>
> With emacs.d, that's another thing. De facto
> often loading from git-repos setting load-path
> and require, not from package-manager.
With emacs.d for me, mostly it contains Elisp
that are loaded explicitely from .emacs.
So I don't see why this wouldn't work for me!
--
underground experts united
http://user.it.uu.se/~embe8573
prev parent reply other threads:[~2018-10-26 10:55 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
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 [this message]
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=86mur1q8nc.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).