Open YousufSSyed opened 1 year ago
+1 to this. I use macros to enable various focus plugins, so pretty obvious when it fires :D
Yes please, it's an unneccessary distraction for me.
I didn't fix it but made it better. It's now just a very short blip.
In your vault folder in explorer or finder go to .obsidian\plugins\obsidian-better-command-palette/
Open main.js. It was very messy for me so in Notepadd++ I used the plugin JSTool, the JSFormat option of that, to tidy it up. But that's not necessary, just simpler.
Ctrl+F for
new e.Notice(Successfully ran "${this.name}"
),
and comment that out with //.
Keep the !0 after it uncommented. Mine looks like this:
It's in the callAllCommands() function. It's better now!
I know it may not be obvious if a macro runs successfully, but sometimes it is when the commands in the macro create their own notifications. Perhaps a user should be able to choose one of three settings: one where notifications are off on all macros, one where they're all on, and one where the user can pick per macro whether it sends a notification.