setHandler Sets as the default handler for a given / combination. getUTIs Returns a list of all known UTIs, and their default handler. getSchemes Returns a list of all known URI schemes, accompanied by their default handler. Learn more about Swift Default Apps at the GitHub link below. NOTE: This guide focuses on setting the default email application however, the Swift Default Apps binary can be used on any application. getApps Returns a list of all registered applications. Swift Default Apps - Version 2 was used for this guide. getHandler Returns the default application registered for the URI Scheme or you specify. You can do a check on the current set apps by running this (swda cli in /bin): /usr/local/bin/swda - getUTIs You then issue the command to swiftdefaultsapps cli (rolled out to /bin folder in this case) to set Excel to open csv files: /usr/local/bin/swda - setHandler -app /Applications/Microsoft Excel.app/ -UTI ma-separated-values-text csv: kMDItemContentType "ma-separated-values-text" This gives you the correct interpreter for the filetype you are trying to set.Įxample for. I run this command first to determine the appropriate file attribute : mdls /path/to/file If someone has the knowledge of linux default checks to address that, that'd be great - it basically boils down to an OS-specific implementation of the isCurrentAppOSDefaultForProtocol XPCOM method.Took me a while to figure this out but changing the filetype needs to be based on the correct attribute information. Anyway, fodder for a separate bug.Īnyway, it sounds like we've established that this is basically a result of bug 1599713. That still doesn't sound great, it feels like really we should be telling the user in some way "hey, you configured your OS to open whatever: links with Firefox but we don't know how to open those links". So in terms of straightforward fixes, we could hide an item referring to the current app, so that only the "choose an app" row shows up. So we list the OS default, plus items that the user has manually added as helper apps. Not tested yet with Rosetta 2, Is Apple silicon ready for SwiftDefaultApps, Rosetta 2 support for SwiftDefaultApps, SwiftDefaultApps on M1 Macbook Air, SwiftDefaultApps on M1 Macbook Pro, SwiftDefaultApps on M1 Mac Mini, SwiftDefaultApps on M1 iMac. IIRC we only have infra to get the system default from the OS - not "all the apps that told the OS they can handle these URIs". Let you view and change default application associations. You can file a separate bug about improving this flow, but it's not straightforward and probably not a priority for now. I think we should always ask users to choose an external app, not to choose between external app and NightlyDebug. Note that I can make isCurrentAppOSDefaultForProtocol("ftp") return true by using swiftdefaultapps to change ftphandler to NightlyDebug.app, but the prompt still shows and ask me if I want to use NightlyDebug to open the ftp link. If that's still happening, that feels like it should be a separate bug to this one, ideally with more details - as the real issue there would be profile selection. The understanding there seems to be that Firefox.app shouldn't be delegating to NightlyDebug.app if they're not using the same profile. We explicitly decided not to deal with that case in bug 1496380 (cf. OK, so what's happening here is that you don't use the profile manager by default and so Firefox starts up with the new URI, and hands the URI back to nightly-debug? If you make nightly-debug the default for ftp URIs, the problem doesn't happen? The result of isCurrentAppOSDefaultForProtocol("ftp") is false and the mismatch is: selfURLįile:///Users/changkershaw/work/gecko/objdir/dist/NightlyDebug.app/ I can also reproduce this by simply ticking the checkbox in the prompt. (In reply to Kershaw Chang from comment #17) Is there a way to provide just the non-default about:config entries for you? Anything else I can provide? Unlike when this first triggered, I can get out of the loop easily with multiple Ctrl+W, so it's easy for me to test. I've been using Nightly for years.Īll other mentions of "ftp" are defaulted in both instances. Test: had to be made true before ftp:// wold work. On a mostly virgin instance, after enabling ftp, the ftp directory appears as expected. Just tried the link again on my main browser instance (83.0a1 () (64-bit)) and tabs started opening. Eventually, I tried Ctrl+W as fast as I could, and was able to overtake the openings. Originally, each time I started FF, tabs kept opening without any input from me. This first occurred on 82.0a1 but on restart it was updated to 83.0a1 In fact, I see that entering simply ftp:/ or ftp:// or ftp:/// takes me to my search engine (duckduckgo) but ftp:///home starts opening tabs. HOWEVER, just now tried ftp://home/pfortin/Downloads and tabs started opening so the target is immaterial. This is the link that came up over and over.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |