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 15:04:05 +0300 [thread overview]
Message-ID: <bdd3ec11-3d96-abfa-4447-8dfbbe42bcab@yandex.ru> (raw)
In-Reply-To: <2124138216.2052980.1666055194810@mail.yahoo.com>
On 18.10.2022 04:06, Mark Harig wrote:
> To reproduce the problem, create a ~/.git/ directory and then
> follow the recipe in the original problem report. Those steps
> take less than 10 minutes to reproduce the problem, using Emacs
> 28.1, bash, and cvs. Please let me know if those steps do not
> reproduce the problem with Emacs 28.1.
When I tried to follow your steps (not in HOME toplevel, though, but in
a subdirectory), I got this:
Debugger entered--Lisp error: (wrong-type-argument sequencep t)
#f(compiled-function (d1 d2) #<bytecode -0xaf17ad190f8dc52>)((Git .
"~/examples/emacs-debbugs-58525/") (CVS . t))
sort(((CVS . t)) #f(compiled-function (d1 d2) #<bytecode
-0xaf17ad190f8dc52>))
vc-responsible-backend("/home/dgutov/examples/emacs-debbugs-58525/tmp3/pro...")
vc-dir("/home/dgutov/examples/emacs-debbugs-58525/tmp3/pro..." nil)
Not sure how you get to the step of being prompted for the backend.
This should be fixed in Emacs 28.2 released in September.
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=51800 says Emacs 29 only,
but it's been backported.
Since you are not seeing the exact error for some reason, it's possible
that your problem has not been fixed still. But try Emacs 28.2 at least.
next prev parent reply other threads:[~2022-10-18 12:04 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
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 [this message]
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=bdd3ec11-3d96-abfa-4447-8dfbbe42bcab@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).