Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Starting a second Gnus -- dangerous?
Date: 03 Oct 2000 18:20:32 -0400	[thread overview]
Message-ID: <m3k8bp4ldl.fsf@multivac.student.cwru.edu> (raw)
In-Reply-To: Jorge Godoy's message of "03 Oct 2000 19:13:11 -0200"

Jorge Godoy <godoy@conectiva.com> writes:
> >>>>> On 03 Oct 2000 18:10:42 -0400, prj@po.cwru.edu (Paul Jarc) said:
>     PJ> You might add a hook function to create a lock file when Gnus starts,
>     PJ> signaling an error if it already exists.  Add another hook for when
>     PJ> Gnus exists to delete the file.
> 
> This way, _HE_ would be safe. And all the other users?

What do you mean?  They can also add these (hypothetical) functions to
the appropriate hooks, if they wish to protect themselves.  Perhaps
you think I meant that all users using this feature would share a lock
file.  I did not.


paul



  reply	other threads:[~2000-10-03 22:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-03 21:04 Kai Großjohann
2000-10-03 22:03 ` Karl Kleinpaste
2000-10-04 18:39   ` Kai Großjohann
2000-10-04 18:46     ` Paul Jarc
2000-10-03 22:10 ` Paul Jarc
2000-10-03 21:13   ` Jorge Godoy
2000-10-03 22:20     ` Paul Jarc [this message]
2000-10-03 21:25       ` Jorge Godoy
2000-10-03 22:32         ` Paul Jarc
2000-10-04 13:17   ` Chris Shenton
2000-10-04 16:22     ` Andreas Fuchs
2000-10-04 16:47     ` David S. Goldberg
2000-10-04 18:41       ` Kai Großjohann
2000-10-04 18:56         ` Laura Conrad
2000-10-05 12:48           ` Kai Großjohann
2000-10-05 15:14             ` Laura Conrad
2000-10-04 17:24     ` Paul Jarc
2000-10-04 18:42     ` Kai Großjohann
2000-10-04 22:17       ` Russ Allbery
2000-10-05  5:31         ` Raja R Harinath
2000-10-04  8:23 ` Christoph Rohland
2000-10-04 18:43   ` Kai Großjohann
2000-10-09  7:25     ` Christoph Rohland

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=m3k8bp4ldl.fsf@multivac.student.cwru.edu \
    --to=prj@po.cwru.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 NNTP newsgroup(s).