From: Alexandru Harsanyi <harsanyi@mac.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: emacs-devel@gnu.org
Subject: Re: vc-dired refresh
Date: Sat, 19 Jan 2008 08:00:47 +0900 [thread overview]
Message-ID: <183A3BD8-BA29-465B-A33C-D75E122B4B72@mac.com> (raw)
In-Reply-To: <18321.7840.682424.490929@kahikatea.snap.net.nz>
On 19 Jan 2008, at 6:48 AM, Nick Roberts wrote:
>
> I've noticed the following problem with vc-dired. Its present in
> Emacs 21.3
> and a bit obscure, so Ij ust present it here for the record.
>
> Sometimes that if you do version control operations outside Emacs, 'g'
> (revert-buffer) in vc-dired doesn't keep track of the changes
> (presumably using
> some internal state).
>
> Here's one (contrived) example of what I'm saying:
>
> From the command line:
>
> 1) cd emacs/src (or your directory for Emacs C files.
>
> 2) touch emacs.c
>
> From Emacs (with cvs-stay-local t)
>
> 3) C-x v d
>
> 4) Dired under VC (directory): ~/emacs/src/<RET>
>
> emacs.c is displayed as modified because the date has changed
>
> From the command line:
>
> 5) cvs status emacs.c
>
> This finds no changes, updates the timestamp in Entries and reports
> that
> emacs.c is up-to-date.
>
> From Emacs
>
> 6) 'g' should show now that emacs.c is not modified but doesn't,
> presumably
> because it doesn't consult the Entries file again.
>
I believe this is related to the vc-workfile-unchanged-p problem I
reported in mid December 2007. Basically vc will consider a file as
changed if its modification time is different than the one recorded
at checkout (or when the file is first loaded).
The problem will also manifest itself in C-x v v prompting you to
checkin the file instead of saying that it is up to date.
Cheers,
Alex.
prev parent reply other threads:[~2008-01-18 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 21:48 vc-dired refresh Nick Roberts
2008-01-18 23:00 ` Alexandru Harsanyi [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=183A3BD8-BA29-465B-A33C-D75E122B4B72@mac.com \
--to=harsanyi@mac.com \
--cc=emacs-devel@gnu.org \
--cc=nickrob@snap.net.nz \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).