From: Tim Johnson <tim@akwebsoft.com>
To: help-gnu-emacs@gnu.org
Subject: Re: [solved]Test Alternative initialize scheme
Date: Sat, 7 Apr 2018 16:27:26 -0800 [thread overview]
Message-ID: <20180408002726.GB2009@mail.akwebsoft.com> (raw)
In-Reply-To: <20180405215706.GD6062@mail.akwebsoft.com>
* Tim Johnson <tim@akwebsoft.com> [180405 14:02]:
> * Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com> [180405 13:50]:
> > There's a script called emacs-distribution on EmacsWiki:
> >
> > https://www.emacswiki.org/emacs/emacs-distribution
> >
> > It achieves the same thing you're trying to do, but using a different method
> > - it presets HOME env variable.
> >
> > Advantage over your setup - configs get ran normally, so even Customize,
> > which gets disabled by -q would work.
> >
> > Disadvantage - you can't refer to subfolders in your ~ from inside of Emacs,
> > I usually symlink the ones I need.
> >
> Thank you. That is one of the sites that I reviewed before
> opening this topic.
So my usage of emacs is pretty limited, since I am "resting on my
laurels", "enjoying a golden sunset", etc.
Thus I discarded the goal of running more than one "kit" at a time
and just set up two launch scripts, one which symlinks my
"standard" .emacs.d (now located elsewhere) to ~/.emacs.d, and the
other symlinks .spacemacs.d to ~/.emacs.d.
It seems to be a workable solution and switching them is very fast on
my machine. For decades I've used both terminal vim (system work via MC)
and Gui-Emacs for coding.
Spacemacs should turn out be a reasonable marriage of two
paradigms - and as my wife would tell me, a reasonable marriage
beats one made in heaven (if indeed any marriages really are).
Seriously, spacemacs seems to be a nice piece of work. Kudos to
the developers.
--
Tim Johnson
http://www.akwebsoft.com, http://www.tj49.com
next prev parent reply other threads:[~2018-04-08 0:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 23:12 Test Alternative initialize scheme Tim Johnson
2018-04-05 21:43 ` Nikolay Kudryavtsev
2018-04-05 21:57 ` Tim Johnson
2018-04-08 0:27 ` Tim Johnson [this message]
[not found] ` <mailman.11759.1522964625.27995.help-gnu-emacs@gnu.org>
2018-04-06 19:06 ` Emanuel Berg
2018-04-06 21:15 ` Nikolay Kudryavtsev
2018-04-07 6:41 ` Eli Zaretskii
2018-04-07 12:38 ` Nikolay Kudryavtsev
2018-04-07 12:53 ` Eli Zaretskii
[not found] ` <mailman.11799.1523049339.27995.help-gnu-emacs@gnu.org>
2018-04-06 21:55 ` Emanuel Berg
2018-04-07 12:20 ` Nikolay Kudryavtsev
2018-04-08 1:43 ` Emanuel Berg
2018-04-08 12:31 ` Nikolay Kudryavtsev
[not found] ` <mailman.11861.1523190672.27995.help-gnu-emacs@gnu.org>
2018-04-08 14:48 ` Emanuel Berg
2018-04-09 17:42 ` Nikolay Kudryavtsev
[not found] ` <mailman.11937.1523295742.27995.help-gnu-emacs@gnu.org>
2018-04-09 18:56 ` Emanuel Berg
2018-04-09 22:24 ` Nikolay Kudryavtsev
[not found] ` <mailman.11951.1523312688.27995.help-gnu-emacs@gnu.org>
2018-04-09 22:44 ` Emanuel Berg
2018-04-09 23:15 ` Nikolay Kudryavtsev
[not found] ` <mailman.11953.1523315732.27995.help-gnu-emacs@gnu.org>
2018-04-09 23:41 ` 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=20180408002726.GB2009@mail.akwebsoft.com \
--to=tim@akwebsoft.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).