From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 58525@debbugs.gnu.org, idirectscm@aim.com
Subject: bug#58525: 28.1: `vc-dir' (key sequence: C-x v d) fails when used with a CVS repository
Date: Mon, 17 Oct 2022 19:34:53 +0300 [thread overview]
Message-ID: <83pmeq1k9e.fsf@gnu.org> (raw)
In-Reply-To: <9490cc5d-5d0f-4ef6-d00b-0629853aaa22@yandex.ru> (message from Dmitry Gutov on Mon, 17 Oct 2022 16:00:25 +0300)
> Date: Mon, 17 Oct 2022 16:00:25 +0300
> Cc: 58525@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
>
> On 17.10.2022 09:06, Eli Zaretskii wrote:
> > AFAIK, the VC's support for CVS is based on detecting the CVS
> > subdirectory of a directory where you invoke vc-dir. If that
> > subdirectory is not found, VC will assume the backend is not CVS. In
> > which case your assumptions seem to be mistaken.
> >
> > But I will let VC expert to chime in here, because I may be wrong or
> > confused.
>
> Here's the basic logic:
>
> (defun vc-cvs-registered (f)
> "Return non-nil if file F is registered with CVS."
> (when (file-readable-p (expand-file-name
> "CVS/Entries" (file-name-directory f)))
> ...
Thanks. So after performing the steps in the original report, I do
have ~/tmp3/project1/CVS/Entries here.
next prev parent reply other threads:[~2022-10-17 16:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2011444375.1250404.1665768998367.ref@mail.yahoo.com>
2022-10-14 17:36 ` bug#58525: 28.1: `vc-dir' (key sequence: C-x v d) fails when used with a CVS repository Mark Harig via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 18:34 ` Eli Zaretskii
2022-10-16 22:06 ` Mark Harig via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-17 6:06 ` Eli Zaretskii
2022-10-17 13:00 ` Dmitry Gutov
2022-10-17 16:34 ` Eli Zaretskii [this message]
2022-10-17 17:43 ` Mark Harig via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-17 23:10 ` Dmitry Gutov
2022-10-18 1:06 ` Mark Harig via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-18 12:04 ` Dmitry Gutov
2022-10-18 15:39 ` Mark Harig via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-18 15:58 ` Dmitry Gutov
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=83pmeq1k9e.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58525@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=idirectscm@aim.com \
/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).