From: James Albert Kanze <james-albert.kanze@vx.cit.alcatel.fr>
Subject: Re: Why can a server not be edited?
Date: 10 Dec 1996 12:04:07 +0100 [thread overview]
Message-ID: <rf5raky3bko.fsf@vx.cit.alcatel.fr> (raw)
In-Reply-To: Kai Grossjohann's message of 10 Dec 1996 11:48:19 +0100
Kai Grossjohann <grossjohann@charly.informatik.uni-dortmund.de> writes:
|> >>>>> James Albert Kanze writes:
|>
|> James> I can get around this easily by deleting the server, then
|> James> creating a new one with the same parameters, but why can I
|> James> not edit the server from the server buffer?
|>
|> I've been bitten by that, too. Seems like you can only edit servers
|> that are closed, so you need to `C' (or is it `D'?) the server first.
I tried both. They effectively changed the status (which was denied to
begin with, since I had already moved the files). I still get the
message "this server can't be edited". (Another question is: where are
these commands documented?)
--
James Kanze home: kanze@gabi-soft.fr +33 (0)3 88 14 49 00
office: kanze@vx.cit.alcatel.fr +33 (0)1 69 63 14 54
GABI Software, Sarl., 8 rue des Francs Bourgeois, F-67000 Strasbourg, France
-- Conseils en informatique industrielle --
next prev parent reply other threads:[~1996-12-10 11:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-12-10 10:38 James Albert Kanze
1996-12-10 10:48 ` Kai Grossjohann
1996-12-10 11:04 ` James Albert Kanze [this message]
1996-12-11 0:29 ` Lars Magne Ingebrigtsen
1996-12-11 0:28 ` Lars Magne Ingebrigtsen
1996-12-11 8:52 ` James Albert Kanze
1996-12-11 9:24 ` Per Abrahamsen
1996-12-11 9:40 ` Lars Balker Rasmussen
1996-12-16 12:50 ` Lars Magne Ingebrigtsen
[not found] ` <tx1n2uqmhdn.fsf@cygnus.com>
[not found] ` <m24tgwnylx.fsf@proletcult.slip.ifi.uio.no>
[not found] ` <tx1wwtran5n.fsf@cygnus.com>
1997-01-07 15:10 ` Lars Magne Ingebrigtsen
1997-01-07 19:04 ` visigoth
1997-01-07 20:24 ` Lars Magne Ingebrigtsen
1997-01-08 6:36 ` visigoth
1997-01-09 10:51 ` Lars Magne Ingebrigtsen
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=rf5raky3bko.fsf@vx.cit.alcatel.fr \
--to=james-albert.kanze@vx.cit.alcatel.fr \
/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).