From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Help with vc-ediff setup
Date: Fri, 10 Mar 2023 09:27:51 +0200 [thread overview]
Message-ID: <837cvp12x4.fsf@gnu.org> (raw)
In-Reply-To: <CAFDHx1LABkYBmRcVGDmn=h_RnJ8Z6LxuZrg2cPGCuYadc+wCaQ@mail.gmail.com> (message from Patrick Mahan on Thu, 9 Mar 2023 13:28:49 -0800)
> From: Patrick Mahan <plmahan@gmail.com>
> Date: Thu, 9 Mar 2023 13:28:49 -0800
>
> A new part of my job is to review code changes made by programmers I have
> been asked to mentor. I would like to use vc-ediff when doing this, but
> unfortunately, due to how IT configures our file permissions, I do not have
> write permission in these users directories. This leads to a failure with
> opening 'file'.~branch~.
>
> I have looked through both the VC+.el and ediff.el for clues but I get
> hopelessly lost. So if there is a way to specify creating these temp files
> under say /tmp or somewhere I have write access, that would be very helpful.
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.
next prev parent reply other threads:[~2023-03-10 7:27 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 [this message]
2023-03-10 7:48 ` Manuel Giraud via Users list for the GNU Emacs text editor
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=837cvp12x4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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).