Re: vc-status vs pcl-cvs

[Dan Nicolaescu]

Stefan Monnier <address@hidden> writes:

  > > So that means you'd want vc-dir to work differently by default than
  > > cvs-status?
  > 
  > Of course.  `cvs-examine' and `cvs-status' are there only for
  > historical reasons.  *THE* entry point to PCL-CVS is cvs-quickdir.

How many people actually know about that/use it?  (I certainly never
heard of it, and it's not in the menu or etc/NEWS so it's not
obvious or easy to find).

  > > That would be surprising for most users.  In the case of being
  > > disconnected, vc-dir can only show you the file states, if they are
  > > edited or not,
  > 
  > Which is indeed all the info you'll ever get from all other VCSes.
  > Their `vc-dir' command will never tell you "needs-update" either.

But the state those backends show in vc-dir is accurate, and you can
just check things in without a problem.  If things go the way you are
proposing, how do you get the up to date state so you can actually check
in your changes?  Another command?  I'd rather not have the users jump
through another hoop by default.

  > > Now, to implement this stuff vc-cvs-dir-status just needs to be changed
  > > to do
  > > (if vc-cvs-stay-local-p
  > >     THE_CODE_FROM-vc-rcs-dir-status
  > >   THE_CURRENT_CODE)
  > 
  > Actually it might be better off using cvs-fileinfo-from-entries.
  > The only shortcoming of cvs-fileinfo-from-entries is that it won't show
  > you the "unknown" files (files that are neither ignored nor under CVS
  > control).

If someone cares enough about this, there's enough information to
implement it.