ibichka

Have you tried using `#+OPTIONS: broken-links:t `to allow exporting with 'allegedly' broken links `(org-export-with-broken-links)`?

Glad it did help! When you export it using `#+OPTIONS: broken-links:t`, do the links work (are they active) in the exported file?

Good to hear.

Thanks so much for the clarification: > The reason the "Public" group doesn't show up is because we've ended up with a feature originally developed for one purpose having unwanted...

Thanks, that's a very handy function right there to do exactly what I meant from within the orgmode domain. I'll keep this updated when I find a way to implement...

I'm having an identical error when performing sim (success) and run (error) for the following rule: ```yaml - name: "DOWNLOADS {files} {moves image types into IMAGE}" locations: ~/Downloads enabled: true...

Thanks, in my case it's not to do with Google Drive, as it just pertains the /Downloads folder in a MacOS system. It never spit this error in earlier versions....

I didn't get asked. I have added `Full Disk Access` and `Files and Folders` permissions to `organize`. Additionally, I've `chmod -R 777 Downloads`, but keeps getting the same error...

Interestingly, I have identical rules like e.g., ```yaml - name: "DOWNLOADS {files} {moves audio types into AUDIO}" locations: ~/Downloads enabled: true filters: - extension: - ogg - mp3 - aiff...

Thanks. Here you have what I see on screen for two identical rules targetting IMAGES or AUDIO files: ```shell ⚙ DOWNLOADS {files} {moves image types into IMAGE} /Users/user/Downloads 2G0A9513copia_1.jpg -...