From: Pankaj Jangid <pankaj.jangid@gmail.com>
To: Emacs mailing list <help-gnu-emacs@gnu.org>
Cc: Perry Smith <pedz@easesoftware.com>
Subject: Re: iCloud directory access issue on macOS Catalina
Date: Sat, 12 Oct 2019 12:43:06 +0530 [thread overview]
Message-ID: <m2tv8e8mil.fsf@gmail.com> (raw)
In-Reply-To: <4EFEE550-90AA-44F9-B226-C5D05C63AAD2@easesoftware.com> (Perry Smith's message of "Fri, 11 Oct 2019 09:09:04 -0500")
Perry Smith <pedz@easesoftware.com> writes:
> Someone at the EmacsForMacOS GitHub discovered a few things about
> this. (Not exactly solved but a relatively simple work around)
>
> Add Emacs.app to "Full Disk Access", then inside Emacs, use
> ns-open-file-using-panel (bound to Cmd-o by default) to open an
> arbitrary **file** directly inside ~/Documents. The GUI won't let you
> open a directory. I bet that could be enhanced a little. After that
> emacs can dired in ~/Documents.
>
I confirm that this approach worked on my Mac.
> There seems to be three of these: ~/Documents, ~/Desktop, and
> ~/Downloads. I'm surprised ~/Downloads is in there because its not
> copied to iCloud.
>
Yes. ~/Downloads is surprising. This implies that the problem isn't
related to iCloud but it is some other permissions stuff, which is
specific to macOS 10.15 (Catalina).
> The ns-open-file-using-panel must be done once for each of these
> three. After that, it appears to work forever and ever. I even
> rebooted and it still worked.
>
>
--
Regards,
Pankaj Jangid
next prev parent reply other threads:[~2019-10-12 7:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 7:06 iCloud directory access issue on macOS Catalina Pankaj Jangid
2019-10-10 16:23 ` Perry Smith
2019-10-11 14:09 ` Perry Smith
2019-10-12 7:13 ` Pankaj Jangid [this message]
2019-10-31 13:39 ` Pankaj Jangid
2019-10-31 14:51 ` Perry Smith
2019-10-31 16:30 ` Pankaj Jangid
2019-10-31 16:53 ` Pankaj Jangid
2019-10-31 18:05 ` Perry Smith
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=m2tv8e8mil.fsf@gmail.com \
--to=pankaj.jangid@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=pedz@easesoftware.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 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.