all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sven Joachim <svenjoac@gmx.de>
To: "Daniel Martín" <mardani29@yahoo.es>
Cc: 59962@debbugs.gnu.org
Subject: bug#59962: 29.0.60; vc commands fail in diff-mode
Date: Sun, 11 Dec 2022 18:18:44 +0100	[thread overview]
Message-ID: <87bko9505n.fsf@turtle.gmx.de> (raw)
In-Reply-To: <m1y1rdlwg8.fsf@yahoo.es> ("Daniel Martín"'s message of "Sun, 11 Dec 2022 17:46:47 +0100")

On 2022-12-11 17:46 +0100, Daniel Martín wrote:

> Sven Joachim <svenjoac@gmx.de> writes:
>
>> As a distribution maintainer, I find myself working with
>> version-controlled patches which Emacs visits in diff-mode.
>> Unfortunately, there is a bad interaction between diff-mode and vc,
>> which makes all vc commands fail.  This is what I got on C-x v l:
>>
>> ,----
>> | Debugger entered--Lisp error: (wrong-type-argument arrayp nil)
>> |   file-truename(nil)
>> |   find-buffer-visiting(nil)
>> |   vc-buffer-sync-fileset((Git (nil nil nil nil) nil nil patch) t)
>> |   vc-diff(nil t)
>> |   funcall-interactively(vc-diff nil t)
>> |   call-interactively(vc-diff nil nil)
>> |   command-execute(vc-diff)
>> `----
>>
>
> Could you detail the steps to reproduce this issue (preferably from
> emacs -Q)?  I've tried C-x v l on a few Git-version-controlled .patch
> files (in Diff mode) but I couldn't reproduce the error.  Thanks.

$ git clone https://salsa.debian.org/xorg-team/app/xterm.git

Then visit any of the xterm/debian/patches/*.diff files and type
C-x v l.

Cheers,
       Sven





  reply	other threads:[~2022-12-11 17:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-11 12:25 bug#59962: 29.0.60; vc commands fail in diff-mode Sven Joachim
2022-12-11 16:46 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-11 17:18   ` Sven Joachim [this message]
2022-12-11 17:28   ` Juri Linkov
2022-12-11 17:24 ` Juri Linkov

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=87bko9505n.fsf@turtle.gmx.de \
    --to=svenjoac@gmx.de \
    --cc=59962@debbugs.gnu.org \
    --cc=mardani29@yahoo.es \
    /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.