From: William Case <billlinux@rogers.com>
To: Pascal Bourguignon <pjb@informatimago.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Two separate emacs running ??
Date: Fri, 17 Aug 2007 12:54:21 -0400 [thread overview]
Message-ID: <1187369661.17619.145.camel@CASE> (raw)
In-Reply-To: <87r6m2ywja.fsf@thalassa.informatimago.com>
Thanks Pascal;
Your suggestions and my last post passed in the night.
On Fri, 2007-08-17 at 18:07 +0200, Pascal Bourguignon wrote:
> William Case <billlinux@rogers.com> writes:
> > Has anybody else done the same?
>
> Yes. Aquamacs uses frames for special purposes intensively, you could
> take example on the code there.
>
>
> > Could you point me to an existing solution?
>
> I would add a find-file-hook and test for these specific files, and in
> the hook set the frame as I want. For merely one file, I wouldn't
> use another emacs instances (though there's one parameter that cannot
> be made different in different frames: the frame border use the same
> face on all frames). Only for a process, since emacs isn't threaded,
> a long operation in a process can freeze emacs for some time, so I may
> use a different emacs for erc and gnus. If you use a different emacs,
> you need to use the window manager to focus on one emacs or another,
> while with a single emacs, you can focus to another frame with C-x 5
> o. But of course, if you use ratpoison, it can be workable, since
> then you can just type C-t o.
>
>
> > [...]
> > I thought of constructing a /.emacs2 file and having a completely new or
> > separate instance of emacs for these files. How would I do that so that
> > emacs2 could find /.emacs2 and not /.emacs on start up, if it is even
> > possible?
>
> Probably. Have you tried man emacs or emacs --help?
>
I started there.
>
>
> What I do, when I want to launch special purpose emacsen, is:
>
> alias special-purpose='emacs --eval "(my-special-purpose-function)"'
>
> and I set the defaults specially in my-special-purpose-function,
> loaded from my normal '~/.emacs'.
>
> I prefer to keep one .emacs (even across different systems!), and test
> inside it for the special circumstances, using these variables and
> others:
>
> ;; system-type darwin gnu/linux cygwin
> ;; system-name "naiad.informatimago.com" "host.example.com"
> ;; system-configuration "i686-pc-linux-gnu" "i686-pc-cygwin"
> ;; window-system nil x mac w32
> ;; emacs-major-version 18 19 20 21
> ;; emacs-minor-version 0 1 2 3
> ;; emacs-version "20.7.2" "21.2.1"
Your suggestions are within the bounds of what I already know (or think
I know, anyways) so I'll try that. Creating a new major mode might be a
reach for me.
--
Regards Bill
next prev parent reply other threads:[~2007-08-17 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4909.1187363917.32220.help-gnu-emacs@gnu.org>
2007-08-17 16:07 ` Two separate emacs running ?? Pascal Bourguignon
2007-08-17 16:54 ` William Case [this message]
2007-08-17 19:33 ` Floyd L. Davidson
2007-08-17 15:18 William Case
2007-08-17 15:36 ` Peter Dyballa
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
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=1187369661.17619.145.camel@CASE \
--to=billlinux@rogers.com \
--cc=help-gnu-emacs@gnu.org \
--cc=pjb@informatimago.com \
/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).