From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: emacs-repository-{version|branch} on Windows
Date: Fri, 04 Nov 2022 22:29:40 +0200 [thread overview]
Message-ID: <83tu3e4g5n.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SQxzOqCT0xyzR04N1GYvrb+1v_TjnisODnG+SeCGj3vWQ@mail.gmail.com> (message from Juanma Barranquero on Fri, 4 Nov 2022 21:08:34 +0100)
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Fri, 4 Nov 2022 21:08:34 +0100
> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
>
> In the past it happened with directories created inside .emacs.d/, though I don't remember the specifics.
Is your ~/.emacs.d directory on the same drive as the system, i.e. on
drive C:\? If so, you will have to take ownership by your user on all
of drive C:\, because these problems will keep happening. Most
probably your user is either a local Administrator or a member of the
Administrators group. In both cases, you will bump into these
problems, until you take ownership of every directory you can.
My best advice is to have your HOME directory and everything else GNU
on a drive different from the system drive -- if you can. Then taking
ownership is easier, because there aren't any protected directories,
and the level of paranoia of Windows itself about non-system drives is
lower.
This is basic Windows system setup, nothing to do with Emacs per se.
next prev parent reply other threads:[~2022-11-04 20:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 18:24 emacs-repository-{version|branch} on Windows Juanma Barranquero
2022-11-04 18:36 ` Juanma Barranquero
2022-11-04 18:51 ` Eli Zaretskii
2022-11-04 18:58 ` Juanma Barranquero
2022-11-04 19:28 ` Stefan Monnier
2022-11-04 20:08 ` Juanma Barranquero
2022-11-04 20:29 ` Eli Zaretskii [this message]
2022-11-04 20:42 ` Juanma Barranquero
2022-11-04 20:47 ` Stefan Monnier
2022-11-04 20:56 ` Eli Zaretskii
2022-11-04 21:09 ` Juanma Barranquero
2022-11-04 21:20 ` Stefan Monnier
2022-11-05 6:24 ` Eli Zaretskii
2022-11-05 11:43 ` Juanma Barranquero
2022-11-05 12:36 ` Eli Zaretskii
2022-11-05 13:20 ` Juanma Barranquero
2022-11-05 15:19 ` Stefan Monnier
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=83tu3e4g5n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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).