From: Dmitry Gutov <dgutov@yandex.ru>
To: Mark Harig <idirectscm@aim.com>, "eliz@gnu.org" <eliz@gnu.org>
Cc: "58525@debbugs.gnu.org" <58525@debbugs.gnu.org>
Subject: bug#58525: 28.1: `vc-dir' (key sequence: C-x v d) fails when used with a CVS repository
Date: Tue, 18 Oct 2022 02:10:01 +0300 [thread overview]
Message-ID: <a0bfa70d-2e6f-bae4-35e7-c47d2332b8f2@yandex.ru> (raw)
In-Reply-To: <259751090.1922936.1666028587272@mail.yahoo.com>
On 17.10.2022 20:43, Mark Harig via Bug reports for GNU Emacs, the Swiss
army knife of text editors wrote:
> So, after finding the CVS backend, the `mapcar' expression, above,
> continues and checks for a Git backend, which it finds in the directory
> that contains tmp3/project1, namely, ~, the home directory. Because
> it found ~/.git/, it sets the variable `dirs' to an erroneous value and
> later logic fails because of this.
>
> What is the solution to this problem? What should the VC
> functions (not just `vc-dir') do when they find more than one VC
> backend indicator in the directory tree? Should it issue an
> error indicating more than one VC backend detected, (since files
> cannot be under the control of multiple VC backends)? Or, should
> it stop after the "most local" VC backend is found and attempt to
> use that?
It tries to use the most specific one, by using the sorting logic at the
end of vc-responsible-backend. That was added in
https://debbugs.gnu.org/42966, which should have made it into Emacs 28.1.
I'm not sure why your CVS value in that list is t and not a string: that
should have been fixed in Emacs 28.1 as well, in revision
bc636515884530f0cab6f.
There was a further fix, though (regarding expanded vs abbreviated file
names) which is only available on master (bug#57777). But I'm not sure
if that comes into play here.
Anyway, are you really using Emacs 28.1? If not, try that, if yes: could
you try building Emacs from master? And seeing whether it fixes your
problem.
next prev parent reply other threads:[~2022-10-17 23:10 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
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 [this message]
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=a0bfa70d-2e6f-bae4-35e7-c47d2332b8f2@yandex.ru \
--to=dgutov@yandex.ru \
--cc=58525@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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).