From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: Preventing multiple startups of Gnus by the same user?
Date: 07 Mar 2000 23:20:58 -0500 [thread overview]
Message-ID: <ltn1oajdn9.fsf@asfast.com> (raw)
In-Reply-To: Jan Vroonhof's message of "07 Mar 2000 21:47:11 +0100"
Jan Vroonhof <vroonhof@math.ethz.ch> writes:
> Lloyd Zusman <ljz@asfast.com> writes:
>
> > under this second XEmacs process. What I'd like to do is for this
> > second Gnus to never start up because there's another one running
> > as the same user ID within a different process.
>
> Does it help if you compile --with-clash-detection (in the hope XEmacs
> would then complain if the second Gnus tries to open .newsrc.eld)
Hmmm ... I'll have to try that the next time I recompile XEmacs. Does
anyone know if I can detect some kind of trappable error if another
Gnus has my .newsrc.eld open when running under an XEmacs that's
compiled with this option?
Thanks for the suggestion!
--
Lloyd Zusman
ljz@asfast.com
prev parent reply other threads:[~2000-03-08 4:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-07 3:49 Lloyd Zusman
2000-03-07 3:55 ` Karl Kleinpaste
2000-03-07 4:04 ` Lloyd Zusman
2000-03-07 4:35 ` Andrew J Cosgriff
2000-03-08 4:18 ` Lloyd Zusman
2000-03-07 20:47 ` Jan Vroonhof
2000-03-08 4:20 ` Lloyd Zusman [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ltn1oajdn9.fsf@asfast.com \
--to=ljz@asfast.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 NNTP newsgroup(s).