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
Aliases #1770
Conversation
I thought this would be an easy merge, but now I think I have something to say about all three commits. Sorry. |
OK, take a look at the latest commits. They blow away The last commit should stop the silly |
OK this needs work:
Should we scrap this and go back to how it was, or keep this and keep the old method as a fallback? |
I did some testing in a stand-alone project, and |
…rking We have to revert back to the 'old' way for socket type files because the NSURL method doens't work
OK, I've made some changes to how this works now. I don't like it 100%, since we fall back to using the 'old' method in the rare cases that we can't get any information form NSURL (this only happens for |
Looks good other than the one comment. I’ll remove that code from my local copy and test the rest for a while. |
- instead of hitting the disk Also, do the same when retrieving NSURL keys (cache all key/values in one call)
It only occurs for fifos and sockets, but the files can still be added to QS
Caused a slight bug where mutableDict ended up being nil
Determines if a given file object can be run (e.g. in a shell) Whilst determining this, also check to make sure the file isn't a pipe/socket
OK, finally figured it out :P Take a look and see what you think |
newLabel = (NSString *)CFBridgingRelease(MDItemCopyAttribute(mdItem, kMDItemDisplayName)); | ||
CFRelease(mdItem); | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why was all this logic removed? Quicksilver plug-ins and Preference Panes have ugly names now. (I’m not too worried about plug-ins.)
I think this is fine, other than the naming of Preference Panes. |
OK, so the changes in this file (the changes to how we retrieve file object info - like the UTI) is related to #1841, and should fix it. Shall we try and get this merged into v.1.2.0 then we'll hopefully be able to do away with any more annoying UTI problems |
Conflicts: Quicksilver/Code-QuickStepInterface/QSSearchObjectView.m
Sure. Just fix my precious preference panes. |
But remove code for giving QSPlugins fancy names
NSURLLocalizedNameKey gives exactly the same as `[[NSFileManager defaultManager] displayNameAtPath:path]`. There's no point hitting the disk again for a pointless reason
Hmmm. Have you tried clearing caches and running this? Preference Panes look good, but I was going to test |
Well spotted, a silly mistake really. See the latest commit for why… oops! On 30 Mai 2014, at 02:17, Rob McBroom notifications@github.com wrote:
|
There was confusion over using the keys and the similarly named (but now-unused) variables E.g. URLIsDirectory vs. NSURLIsDirectoryKey
P.S. is it just me, or is file browser now blazingly faster? That needs to go in the changelog ;-) |
Cool. I’ve merged this into my day-to-day build. I’ll try it for a while, but don’t see any issues now. As for speed, I can’t tell much of a difference, but it certainly isn’t slow. (I usually check by arrowing into |
Yep, it’ll need some testing. Since QSUTIWithLSInfoRec and NSURL’s NSURLTypeIdentifierKey give different values for the “Fast Logout.sh” script, I have no doubt that there will be discrepancies in other places. But hopefully, any discrepancies will be for the better On 30 Mai 2014, at 10:43, Rob McBroom notifications@github.com wrote:
|
3 small things:
(alias)
onto the details of alias objectsNSWorkspace
(implications unknown, but my guess is it's an improvement)