Skip to content
Snippets Groups Projects
Commit 99063cd4 authored by ram's avatar ram
Browse files

Changed MAYBE-RCS-CHECK-CHECK-OUT-FILE and status line hackery to call

FILE-WRITABLE on the PROBE-FILE result, since it may be that the file found by
probe-file is not the one that would be written to.
parent b3a23085
No related branches found
No related tags found
No related merge requests found
;;; -*- Package: HEMLOCK; Mode: Lisp -*-
;;;
;;; $Header: /Volumes/share2/src/cmucl/cvs2git/cvsroot/src/hemlock/rcs.lisp,v 1.23 1991/11/09 13:20:14 ram Exp $
;;; $Header: /Volumes/share2/src/cmucl/cvs2git/cvsroot/src/hemlock/rcs.lisp,v 1.24 1991/12/20 00:03:13 ram Exp $
;;;
;;; Various commands for dealing with RCS under Hemlock.
;;;
......@@ -211,7 +211,8 @@
(setf pathname new-name))))))
(cond
((and (not always-overwrite-p)
(probe-file pathname) (ext:file-writable pathname))
(let ((pn (probe-file pathname)))
(and pn (ext:file-writable pn))))
;; File exists and is writable so check and see if the user really
;; wants to check it out.
(command-case (:prompt
......@@ -453,7 +454,7 @@
(if (probe-file rcs-file)
;; This is an RCS file
(let ((probe-file (probe-file pathname)))
(cond ((and probe-file (file-writable pathname))
(cond ((and probe-file (file-writable probe-file))
:locked)
((or (not probe-file)
(< (file-write-date pathname)
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment