Gnus development mailing list
 help / color / mirror / Atom feed
From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: Preventing multiple startups of Gnus by the same user?
Date: 06 Mar 2000 23:04:15 -0500	[thread overview]
Message-ID: <lt8zzvfmtc.fsf@asfast.com> (raw)
In-Reply-To: Karl Kleinpaste's message of "06 Mar 2000 22:55:04 -0500"

Karl Kleinpaste <karl@justresearch.com> writes:

> Lloyd Zusman <ljz@asfast.com> writes:
> > Does there already exist a reliable way to tell either before or
> > during Gnus startup that the same user on the same machine already
> > has a Gnus session running?
> 
> Cf. gnus-alive-p.

OOPS ... I'm sorry, but I wasn't clear enough in my original question,
although thank you very much for your quick reply.

I'll try to do a better job with my question:

Suppose I have started up XEmacs as a certain user on my machine, and
this XEmacs process is running Gnus.  Now, suppose I forget that this
original XEmacs process is evan running and I start XEmacs up all over
again under that same user ID.  Now, suppose I try to start Gnus
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.

Unless I'm mistaken, `gnus-alive-p' only checks for an already-running
Gnus within a single XEmacs process.

If this cannot be done directly using Gnus, perhaps XEmacs provides some
functions that I can use to implement this ... ???

Thanks again in advance ...

-- 
 Lloyd Zusman
 ljz@asfast.com



  reply	other threads:[~2000-03-07  4:04 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 [this message]
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

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=lt8zzvfmtc.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).