From: Jorge Godoy <godoy@conectiva.com>
Cc: ding@gnus.org
Subject: Re: Starting a second Gnus -- dangerous?
Date: 03 Oct 2000 19:25:56 -0200 [thread overview]
Message-ID: <kpr95xvcpn.fsf@dagon.casa> (raw)
In-Reply-To: <m3k8bp4ldl.fsf@multivac.student.cwru.edu>
>>>>> On 03 Oct 2000 18:20:32 -0400, prj@po.cwru.edu (Paul Jarc) said:
PJ> What do you mean? They can also add these (hypothetical) functions to
PJ> the appropriate hooks, if they wish to protect themselves. Perhaps
PJ> you think I meant that all users using this feature would share a lock
PJ> file. I did not.
You didn't get my point. (I admint I didn't explained it so you could
see what I meant ;-) sorry)
Suppose that I'm a newbie at Emacs and Gnus (I'm a newbie at Gnus). I
won't be protected by default. There should be a default function to
protect me -- newbie --, or it should be safe to have 2 gnusae running
simultaneously.
I think that one should not bet on the user to make things safe at his
side...
See you,
--
Godoy. <godoy@conectiva.com>
Departamento de Publicações Conectiva S.A.
Publishing Department Conectiva Inc.
next prev parent reply other threads:[~2000-10-03 21:25 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
2000-10-03 21:25 ` Jorge Godoy [this message]
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=kpr95xvcpn.fsf@dagon.casa \
--to=godoy@conectiva.com \
--cc=ding@gnus.org \
/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).