From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Tim Johnson Newsgroups: gmane.emacs.help Subject: Re: Test Alternative initialize scheme Date: Thu, 5 Apr 2018 13:46:53 -0800 Organization: AkWebsoft Message-ID: <20180405214653.GC6062@mail.akwebsoft.com> References: <86o9iytrsp.fsf@zoho.com> <86po3e4f1o.fsf@zoho.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: blaine.gmane.org 1522964728 1985 195.159.176.226 (5 Apr 2018 21:45:28 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 5 Apr 2018 21:45:28 +0000 (UTC) User-Agent: Mutt/1.9.4 (2018-02-28) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Apr 05 23:45:24 2018 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1f4Ch8-0000Pe-Tn for geh-help-gnu-emacs@m.gmane.org; Thu, 05 Apr 2018 23:45:24 +0200 Original-Received: from localhost ([::1]:56868 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f4CjE-0001ww-DM for geh-help-gnu-emacs@m.gmane.org; Thu, 05 Apr 2018 17:47:32 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34748) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f4Cih-0001wY-3A for help-gnu-emacs@gnu.org; Thu, 05 Apr 2018 17:47:00 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f4Cie-00013D-0n for help-gnu-emacs@gnu.org; Thu, 05 Apr 2018 17:46:59 -0400 Original-Received: from tjohnson.mtaonline.net ([64.4.232.191]:36014) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f4Cid-00010z-N0 for help-gnu-emacs@gnu.org; Thu, 05 Apr 2018 17:46:55 -0400 Original-Received: by linus (Postfix, from userid 1000) id E2367240014; Thu, 5 Apr 2018 13:46:53 -0800 (AKDT) Mail-Followup-To: help-gnu-emacs@gnu.org Content-Disposition: inline In-Reply-To: <86po3e4f1o.fsf@zoho.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 64.4.232.191 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:116362 Archived-At: * Emanuel Berg [180404 17:30]: > Tim Johnson wrote: > > > I'm not sure how one might combine spacemacs > > and emacs resources under one directory. > > The spacemacs install directions call for > > installing spacemacs directly into .emacs.d > > and I'm presuming that will totally clobber > > my existing config. > > OK, sorry, now I understand the problem! > If this is what you mean by "clutter" it is > very poor engineering indeed! Unbelievable - > you should mail the developers and tell them! > > *Yes* you should definitely change it! > > I'd do it like this: Do a grep for any > reference to .emacs.d in the spacemacs source > and instalation scripts, Makefiles etc. If it > is a variable somewhere, change it, to > .spacemacs.d - and if it isn't, change > every occurence. I could do that and see what happens, probably will. However, the preferred installation sidesteps that process. I installed spacemacs with the following preferred command: git clone https://github.com/syl20bnr/spacemacs ~/.emacs.d git will not overwrite .emacs.d, so I had to rename it (was already backed up elsewhere). Spacemacs seems to be put together quite professionally. I believe that I could merge the the new .emacs.d and my current one without anything getting clobbered except for init.el. So the option of a custom init file is doable. It is probably best to just investigate further and submit questions to the spacemacs IRC before I do any merging. I couple of simple scripts should handle that. I'm an eternal noob on emacs and even more rusty since I retired my coding business *but*, I think that spacemacs could have put this together with transitions from older, established emacsen in mind. Their installation instructions seem to procede from only one scenario: Newbie doesn't have emacs, noobie installs emacs and spacemacs on top of that fresh install and it's good to go. Not so easy for someone like me who has a collection of legacy resources. Thanks for the help, Emanuel. If you like, in a few days, I can post an update, this time with spacemacs in the subject. cheers > Then you might need to tell spacemacs to look > there, as well. > > -- > underground experts united > http://user.it.uu.se/~embe8573 -- Tim Johnson http://www.akwebsoft.com, http://www.tj49.com