emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: vc-mode permissions problems on NT


From: David Abrahams
Subject: Re: vc-mode permissions problems on NT
Date: Wed, 10 Sep 2003 09:25:55 -0400
User-agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (windows-nt)

Andre Spiegel <address@hidden> writes:

> On Tue, 2003-09-09 at 20:30, David Abrahams wrote:
>
>> Here's an example.  CVS/Entries says:
>> 
>>        /convenience.cpp/1.2/Thu May  8 02:17:51 2003//
>> 
>> and dired says:
>> 
>>       -r--r--r--   1 dave     root     1666 05-07 22:17 convenience.cpp
>> 
>> What does that mean?
>
> This probably means that the timestamps agree (CVS always has it in UTC,
> and your timezone appears to be 4 hours behind it).  It's very strange
> that VC would still consider the file to be "edited".  Is it possible
> for you to step through vc-cvs-state and vc-cvs-state-heuristic in the
> debugger?  

In vc-cvs-state-heuristic, (file-attributes file) yields:

   (nil 1 5 5 (16223 9039) (15707 62723) (15938 41615) 199 "-r--r--r--" nil 
17944 (48170 . 6007))


(equal checkout-time lastmod) yields:

       nil

vc-cvs-state doesn't seem to be getting invoked.


The backtrace leading here looks like:

  vc-cvs-state-heuristic("c:/boost/libs/python/todo.html")
  apply(vc-cvs-state-heuristic "c:/boost/libs/python/todo.html")
  vc-call-backend(CVS state-heuristic "c:/boost/libs/python/todo.html")
  vc-state("c:/boost/libs/python/todo.html")
  vc-default-mode-line-string(CVS "c:/boost/libs/python/todo.html")
  vc-cvs-mode-line-string("c:/boost/libs/python/todo.html")
  apply(vc-cvs-mode-line-string "c:/boost/libs/python/todo.html")
  vc-call-backend(CVS mode-line-string "c:/boost/libs/python/todo.html")
  vc-mode-line("c:/boost/libs/python/todo.html")
  vc-find-file-hook()
  run-hooks(find-file-hook)
  after-find-file(nil t)
  find-file-noselect-1(#<buffer todo.html> "c:/boost/libs/python/todo.html" nil 
nil "c:/boost/libs/python/todo.html" (23121 (48170 . 6007)))
  find-file-noselect("c:/boost/libs/python/todo.html" nil nil t)
  ad-Orig-find-file("c:/boost/libs/python/todo.html" t)
  find-file("c:/boost/libs/python/todo.html" t)
* call-interactively(find-file)
  recursive-edit()
  (lambda (buf) (view-buffer buf (lambda ... ...)) (recursive-edit) 
nil)(#<killed buffer>)
  funcall((lambda (buf) (view-buffer buf (lambda ... ...)) (recursive-edit) 
nil) #<killed buffer>)
  (if (funcall (aref def 0) elt) (setq actions (1+ actions)) (setq next (\` 
...)))
  (cond ((eq def ...) (setq next ...)) ((eq def ...) (funcall actor elt) (setq 
actions ...)) ((eq def ...)) ((eq def ...) (funcall actor elt) (setq actions 
... next ...)) ((eq def ...) (setq quit-flag t) (setq next ...)) ((eq def ...) 
(if ... ...) (while ... ...)) ((eq def ...) (with-output-to-temp-buffer 
"*Help*" ... ...) (setq next ...)) ((vectorp def) (if ... ... ...)) ((and ... 
...) (setq delayed-switch-frame char) (setq next ...)) (t (message "Type %s for 
help." ...) (beep) (sit-for 1) (setq next ...)))
  (cond ((stringp prompt) (setq quit-flag nil) (if use-menus ... ... ...) (cond 
... ... ... ... ... ... ... ... ... ...)) (prompt (funcall actor elt) (setq 
actions ...)))
  (while (funcall next) (setq prompt (funcall prompter elt)) (cond (... ... ... 
...) (prompt ... ...)))
  (progn (if (stringp prompter) (setq prompter ...)) (while (funcall next) 
(setq prompt ...) (cond ... ...)))
  (unwind-protect (progn (if ... ...) (while ... ... ...)) (if 
delayed-switch-frame (setq unread-command-events ...)))
  (let* ((actions 0) user-keys mouse-event map prompt char elt tail def 
use-menus delayed-switch-frame (next ...)) (if (and ... use-dialog-box) (let 
... ...) (setq user-keys ... map ...)) (unwind-protect (progn ... ...) (if 
delayed-switch-frame ...)) (let (...) (message "")) actions)
  map-y-or-n-p(#[(buffer) "\305!\205P

> I'd have to know what these functions do when you open an
> unmodified file.  (They ought to realize that the timestamps agree, and
> that the file is therefore not edited.  I need to find out why this
> isn't the case here.)

Maybe the unexpected bytpass of vc-cvs-state is the problem?

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com





reply via email to

[Prev in Thread] Current Thread [Next in Thread]