generated from obsidianmd/obsidian-sample-plugin
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Write breadcrumbs to *ALL* files command does nothing #217
Comments
I've added a patch to this command. I don't think it will be perfect yet, but it should now work for most files, and it will console log the files it doesn't work for |
Give it a try and let me know how it works :) |
Will do, thanks for all your efforts! Planning to showcase your plugin on
youtube.
…On Mon, Jan 3, 2022, 20:48 SkepticMystic ***@***.***> wrote:
Give it a try and let me know how it works :)
—
Reply to this email directly, view it on GitHub
<#217 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANCXWTGYJIPXM7GCRQ4MRI3UUGZNTANCNFSM5KJP3URA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID:
***@***.***>
|
@omarali-koy that'll be awesome! Please do share the link once you've had a chance :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(Using current version, 2.12.1)
The "Write breadcrumbs to ALL files" command isn't working for me. When I try to use it, nothing happens and the log shows no activity. The basic "Write breadcrumbs to current file" command works as expected with no issues.
I tried creating a fresh vault with only the Breadcrumbs and MetaEdit community plugins installed, but got the same result.
The text was updated successfully, but these errors were encountered: