Re: [PATCH] Disable VC when Emacs is noninteractive -batch

[David Kastrup <dak@gnu.org>]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: David Kastrup <dak@gnu.org>
>> Date: Mon, 06 Aug 2007 21:16:44 +0200
>> Cc: Michael Olson <mwolson@gnu.org>, emacs-devel@gnu.org
>> 
>> > Actually I think this is a "feature" of VC which we should tame
>> > significantly: basically, this only makes sense under RCS (and maybe SCCS)
>> > but happens to be in the generic part of VC, so it can bite at any time when
>> > used with other backends.  The idea was that under RCS if a file <foo> is
>> > absent but RCS/<foo>,v is present, than <foo> is virtually present, except
>> > it needs to be checkout first.
>> 
>> That does not even make sense in RCS for me.  One locks files, but
>> does not delete them.
>
> AFAIR, with RCS, when you checkin a file, the work copy is deleted
> unless you use the -u or -l switch.  So it's quite normal to have no
> working file at all.

Indeed, ci(1).  Wow, that is really sick.  Anyway, the normal behavior
for Emacs is to keep locked files around, so I'd say we should cater
for that case primordinarily.  If that means some slight inconvenience
in "classical" RCS use from the command line, presumably not getting
notice of the virtual file presence until checked out, it should be
something we can live with.

I don't think that many people use RCS from command line and from
within Emacs interspersed.

-- 
David Kastrup