unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Barry Margolin <barmar@alum.mit.edu>
Subject: Re: [Q] Several emacs instances / dired and "derived" buffers
Date: Thu, 27 May 2004 12:15:32 -0400	[thread overview]
Message-ID: <barmar-DD558B.12153227052004@comcast.dca.giganews.com> (raw)
In-Reply-To: mailman.7759.1085670886.1061.help-gnu-emacs@gnu.org

In article <mailman.7759.1085670886.1061.help-gnu-emacs@gnu.org>,
 "Ames Andreas (MPA/DF)" <Andreas.Ames@tenovis.com> wrote:

>    Does it make sense to have sevaral instances of emacs running?  How
>    can I start emacs with a separate startup file (and not my default
>    .emacs)?  How can I make sure that gnuclient and friends finds only
>    my emacs-for-editing instance?  Are there other potential problems
>    I do not recognise yet?

You can use the -q option to prevent emacs from reading the default 
.emacs file, and -l filename to make it load a specific file.  So your 
gnus instance could be started up with something like:

emacs -q -l ~/.gnus.elc

Just make sure that only your init file for the emacs-for-editing 
instance executes (gnuserve) to start up the server for gnuclient.

You'll probably want the init files to give the windows distinct title 
bars.

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***

       reply	other threads:[~2004-05-27 16:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.7759.1085670886.1061.help-gnu-emacs@gnu.org>
2004-05-27 16:15 ` Barry Margolin [this message]
     [not found] ` <wkaczo1rjv.fsf@smsoft.ixy.de>
     [not found]   ` <40BD062A.7070205@yahoo.com>
2004-06-18  8:32     ` [Q] Several emacs instances / dired and "derived" buffers Michael Schierl
2004-06-21 15:13       ` Kevin Rodgers
2004-05-27 10:22 Ames Andreas (MPA/DF)
2004-05-29 12:11 ` Kai Grossjohann

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=barmar-DD558B.12153227052004@comcast.dca.giganews.com \
    --to=barmar@alum.mit.edu \
    /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).