From: Manuel Giraud via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Help with vc-ediff setup
Date: Fri, 10 Mar 2023 08:48:35 +0100 [thread overview]
Message-ID: <871qlx59nw.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <837cvp12x4.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 10 Mar 2023 09:27:51 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
[...]
> To allow a more efficient help, would you please show a backtrace from
> the "failure with opening 'file'.~branch~"? It is hard to help
> efficiently without even knowing which function signals the error (if
> indeed that is your problem), and reproducing your situation with the
> few details you posted is not very trivial, either.
BTW, I've just tried to reproduce and it works for me: the
'file'.~branch~ is just a buffer with no file associated (so no
permissions issue). So, as Eli said, we need to know more.
--
Manuel Giraud
prev parent reply other threads:[~2023-03-10 7:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 21:28 Help with vc-ediff setup Patrick Mahan
2023-03-10 7:27 ` Eli Zaretskii
2023-03-10 7:48 ` Manuel Giraud via Users list for the GNU Emacs text editor [this message]
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=871qlx59nw.fsf@ledu-giraud.fr \
--to=help-gnu-emacs@gnu.org \
--cc=eliz@gnu.org \
--cc=manuel@ledu-giraud.fr \
/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.
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).