Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

May I create a Raycast extension from this repo? #4

Open
sfkmk opened this issue Dec 12, 2024 · 2 comments
Open

May I create a Raycast extension from this repo? #4

sfkmk opened this issue Dec 12, 2024 · 2 comments

Comments

@sfkmk
Copy link

sfkmk commented Dec 12, 2024

I want to create a raycast extension based on this repo. If you agree, how should I give you credit?

@nicolodiamante
Copy link
Owner

Hi @sfkmk,

Thanks for reaching out! Your Raycast extension idea sounds great—feel free to use the repo! For credit, you can link back to the Repo and mention me with my GitHub profile and website (nicolodiamante.com). The repo and my site should give you all the context you need, but let me know if I can help with anything else!

@sfkmk
Copy link
Author

sfkmk commented Dec 16, 2024

Thank you for answering! I have a question before proceeding. Beforehand, I'm on Sequoia, didn't test it on other Versions.
Have you noticed that file operations (copying, moving, deleting) cannot be applied to elements in folders marked as "No Sync"? I tested this, and it seems to be because iCloud doesn't handle hidden folders the same way as in the rest of the file system. My idea was that this could be circumvented by adding a dedicated location to the No Sync commands. My suggestion for this would be "~/.nosyncfolder".
The selected item is then moved to the folder and the alias points to it. This doesn't matter for storage usage and doesn't change anything about the behavior in iCloud, since even atm, the entire item needs to be re-synchronized when No Sync is undone. This change would fix the issue with file operations.

What's your opinion on this? Should I make a PR with the change?

Below a picture of the error I referenced:
CleanShot 2024-12-16 at 17 46 53@2x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants