unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Test Alternative initialize scheme
Date: Thu, 05 Apr 2018 03:15:16 +0200	[thread overview]
Message-ID: <86woxm4fob.fsf@zoho.com> (raw)
In-Reply-To: mailman.11718.1522889734.27995.help-gnu-emacs@gnu.org

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.

That shouldn't happen. How did you install
Emacs/spacemacs? Do you use a package manager?
I'm on Raspbian which is Debian for the R-Pi,
one can say, and I don't get any hits for
"spacemacs". However that isn't an excuse for
the developers to mess up a typical Emacs
init/config dir because they now where it is,
for sure. Does that really happen?

-- 
underground experts united
http://user.it.uu.se/~embe8573


  parent reply	other threads:[~2018-04-05  1:15 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.11717.1522883541.27995.help-gnu-emacs@gnu.org>
2018-04-05  0:34 ` Test Alternative initialize scheme Emanuel Berg
2018-04-05  0:55   ` Tim Johnson
2018-04-05  1:09   ` Emanuel Berg
     [not found]   ` <mailman.11718.1522889734.27995.help-gnu-emacs@gnu.org>
2018-04-05  1:15     ` Emanuel Berg [this message]
2018-04-05  1:28     ` Emanuel Berg
2018-04-05 15:15       ` Tim Johnson
2018-04-05 21:46       ` Tim Johnson
     [not found]       ` <mailman.11760.1522964821.27995.help-gnu-emacs@gnu.org>
2018-04-06 18:57         ` Emanuel Berg
2018-04-04 23:12 Tim Johnson
2018-04-05 21:43 ` Nikolay Kudryavtsev
2018-04-05 21:57   ` Tim Johnson
     [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=86woxm4fob.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).