Repository navigation
MacVim exports standard UTIs, and does it wrongly, messing up the system #916
Description
Instructions: Replace the template text and remove irrelevant text (including this line)
Describe the bug
MacVim exports standard UTIs, such as com.adobe.postscript. This is wrong, they should be imported, as they are defined by the system. What is worse, the declaration is seriously wrong. It declares the UTI as conforming to to public.plain-text. THIS IS WRONG it should conform to public.data and public.composite-content. This messes up the system seriously. For instance, when an app checks a UTI, it should use conformsTo to do so, and this will match public-plain-text for postscript, breaking the (other!) app. So you are actually sabotaging other apops and the system.
To Reproduce
In an (other!) app, check an UTI (for instance when writing data from a document based cocoa app) against com.adobe.postscript or public.plain-text (if both are supported)
Expected behavior
This should always match com.adobe.postscript when the type is com.adobe.postscript, and should match public.plain-text for public.plain-text.
Actual Behavior
When comparing public.plain-text against com.adobe.postscript, it now matches (conforms to), even if it should not.
Screenshots
If applicable, copy/paste the text or add screenshots to help explain your problem.
Environment (please complete the following information):
- Vim version [e.g. 8.1.1234] (Or paste the result of
vim --version.) - OS: [e.g. Ubuntu 18.04, Windows 10 1809, macOS 10.14]
- Terminal: [e.g. GNOME Terminal, mintty, iTerm2, tmux, GNU screen] (Use GUI if you use the GUI.)
Additional context
Don't ever sabotage the system.
Activity
eirnym commentedon Jun 29, 2019
Confirm this. There's an official page with the list.
ychin commentedon Jul 17, 2019
This does look pretty busted. The last changes to the UTI were done 10 years ago in 2009 (!). Better late than never fix this I guess.
amcgregor commentedon Jul 23, 2019
Can confirm, weird, weird behaviour on my system. I can't exactly pin the cause to MacVim, but for some reason, many of the "plain text files" (e.g.
.txtfiles, but also unknown likely-to-be-text files) now offer a truly bizarre range of Open With… options. Almost none of which are tools to edit text files, let alone open files at all. Right-clicking a .txt file on my desktop gives:Legend: red are development tools that don't edit files. Yellow are browsers. Teal are editors, but not of plain text content. Hot pink are systems emulators, only opening binary ROM or disk images. Dark hot pink is inexplicable. (Ignore Cathode, it actually is also a plain text editor… wrapped in a too-sexy classic CRT UI. ;)
11 remaining items
Register missing document types for modern dev formats and dotfiles
Register missing document types for modern dev formats and dotfiles
Register missing document types for modern dev formats and dotfiles