From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: William Case <billlinux@rogers.com>
Cc: EMACS List <help-gnu-emacs@gnu.org>
Subject: Re: Two separate emacs running ??
Date: Fri, 17 Aug 2007 17:36:56 +0200 [thread overview]
Message-ID: <20448E3B-574E-43B3-B227-AB81E5A0AFD2@Web.DE> (raw)
In-Reply-To: <1187363926.17619.118.camel@CASE>
Am 17.08.2007 um 17:18 schrieb William Case:
> I thought of constructing a /.emacs2 file
Think of a second login account with its own ~/.emacs or user init file.
Think of putting the fontify code into the system init file and
launch the second GNU Emacs without loading the system init file.
Consider putting the fontify code into a separate Elisp file and and
load this file only into one GNU Emacs.
You could also launch GNU Emacs and make it evaluate some Elisp code
from the command line. Depending on this your init file can provide
the fontify code or not.
--
Greetings
Pete
The most exciting phrase to hear in science, the one that heralds new
discoveries, is not "Eureka!" (I found it!) but "That's funny..."
Isaac Asimov
next prev parent reply other threads:[~2007-08-17 15:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 15:18 Two separate emacs running ?? William Case
2007-08-17 15:36 ` Peter Dyballa [this message]
2007-08-17 16:40 ` William Case
[not found] ` <mailman.4910.1187365029.32220.help-gnu-emacs@gnu.org>
2007-08-17 16:09 ` Pascal Bourguignon
2007-08-17 18:39 ` Eli Zaretskii
[not found] <mailman.4909.1187363917.32220.help-gnu-emacs@gnu.org>
2007-08-17 16:07 ` Pascal Bourguignon
2007-08-17 16:54 ` William Case
2007-08-17 19:33 ` Floyd L. Davidson
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=20448E3B-574E-43B3-B227-AB81E5A0AFD2@Web.DE \
--to=peter_dyballa@web.de \
--cc=billlinux@rogers.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).