From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Independent differently-configured instances running concurrently
Date: Mon, 28 Apr 2014 18:54:04 +0200 [thread overview]
Message-ID: <87eh0h75ub.fsf@web.de> (raw)
In-Reply-To: b89be8ab-9842-4182-aafc-c3b73a0a18f2@googlegroups.com
Hans BKK <hansbkk@gmail.com> writes:
> I'm investigating how to run completely separate instances of emacs
> concurrently.
> #!/bin/bash
> HOME=$HOME/emacs/homes/vanilla
> export PATH="~/.cask/bin:$PATH"
> /bin/bash
> # emacs
I would prefer using different Unix users, too.
In general, however, I think your approach would work, but I'm not
sure. (BTW, should not HOME be the variable to be exported? Why do you
run bash recursively?)
next prev parent reply other threads:[~2014-04-28 16:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 15:39 Independent differently-configured instances running concurrently Hans BKK
2014-04-28 15:43 ` David Hume
2014-04-29 15:23 ` W. Greenhouse
2014-04-28 16:47 ` Javier
2014-04-28 16:54 ` Michael Heerdegen [this message]
2014-04-28 23:17 ` Hans BKK
2014-04-29 0:10 ` Michael Heerdegen
2014-04-29 0:18 ` Robert Thorpe
2014-04-29 0:36 ` Hans BKK
2014-04-29 18:12 ` Hans BKK
2014-04-29 20:24 ` W. Greenhouse
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=87eh0h75ub.fsf@web.de \
--to=michael_heerdegen@web.de \
--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).