all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tim Van Holder <tim.vanholder@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 4599@emacsbugs.donarmstrong.com, Dan Nicolaescu <dann@ics.uci.edu>
Subject: bug#4599: 23.1.50; VC (CVS) fails to show directory status
Date: Thu, 1 Oct 2009 10:38:28 +0200	[thread overview]
Message-ID: <d69e7f6a0910010138t32b8ee4bv839e68eb376db36f@mail.gmail.com> (raw)
In-Reply-To: <jwvfxa33liy.fsf-monnier+emacsbugreports@gnu.org>

2009/10/1 Stefan Monnier <monnier@iro.umontreal.ca>:
> The patch below indeed seems to fix the problem.
>
> [snip]

Yes, this morning's CVS build works fine again.

I still have a couple outstanding issues with VC (CVS backend):

- Sometimes after checking in (either C-x v v in a file, or from
vc-dir), I get "point before start of properties". The commit will
have succeeded at that point (so it's not a big deal as such), but the
mode line of a buffer visiting a checked-in file will not be updated
to indicate its "unmodified" status (i.e. will have "CVS:1.blah"
instead of "CVS-1.blah").
- Some operations, when done on a directory name in vc-dir fail; for
example, I just pressed '+' when on a directory name (containing only
'need-update' files), and got the error "vc-cvs-merge-news: Couldn't
analyze cvs update result". The *vc* buffer has normal CVS output at
that point ("cvs update: Updating ." followed by a bunch of P lines);
my guess it's that first line that confuses VC. Again, the operation
does indeed succeed, so it's not a big deal.

I'll report these as separate bugs once they annoy me enough.





  reply	other threads:[~2009-10-01  8:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30 12:55 bug#4599: 23.1.50; VC (CVS) fails to show directory status Tim Van Holder
2009-09-30 16:53 ` Dan Nicolaescu
2009-09-30 19:59   ` Stefan Monnier
2009-10-01  2:19     ` Stefan Monnier
2009-10-01  8:38       ` Tim Van Holder [this message]
2009-10-01 14:11         ` Stefan Monnier
2009-10-01 16:22           ` Dan Nicolaescu

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=d69e7f6a0910010138t32b8ee4bv839e68eb376db36f@mail.gmail.com \
    --to=tim.vanholder@gmail.com \
    --cc=4599@emacsbugs.donarmstrong.com \
    --cc=dann@ics.uci.edu \
    --cc=monnier@iro.umontreal.ca \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.