You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having (some) files unsupported by the plugin but with UTIS included in "public.audiovisual-content" makes quicklook previews/file moves etc hang indefinitely
#119
Open
AuroraWright opened this issue
Nov 12, 2023
· 1 comment
Maybe related to #112
I noticed that having (as an example) .mid or .sf2 (soundfont files) in my Downloads folder (which I also have as a stack in the Dock) makes quicklook previews hang indefinitely (not sure if only for the current folder, as an example my Dock ~/Downloads stack eventually turns into a bunch of empty boxes) and the affected files can't be moved/renamed etc.
As it turns out, both of those are included in "public.audiovisual-content":
As far as I can tell, removing the affected files/extensions is the only way to prevent this from happening with the quicklook extension active.
The text was updated successfully, but these errors were encountered:
AuroraWright
changed the title
Having (some) files unsupported by the app but with UTIS included in "public.audiovisual-content" makes quicklook previews/file moves etc hang indefinitely
Having (some) files unsupported by the plugin but with UTIS included in "public.audiovisual-content" makes quicklook previews/file moves etc hang indefinitely
Nov 12, 2023
Maybe related to #112
I noticed that having (as an example) .mid or .sf2 (soundfont files) in my Downloads folder (which I also have as a stack in the Dock) makes quicklook previews hang indefinitely (not sure if only for the current folder, as an example my Dock ~/Downloads stack eventually turns into a bunch of empty boxes) and the affected files can't be moved/renamed etc.
As it turns out, both of those are included in "public.audiovisual-content":
.mid:
.sf2:
As far as I can tell, removing the affected files/extensions is the only way to prevent this from happening with the quicklook extension active.
The text was updated successfully, but these errors were encountered: