Reset the local, user and system domains: Lsregister -kill -r -domain local -domain user Run lsregister and display help lsregister PATH=/System/Library/Frameworks/amework/Frameworks/amework/Support:"$PATH" Or temporarily add the directory to your PATH so that you can run lsregister with just lsregister Lsregister is not on the system path so either:Ĭreate an alias 'lsr' for the full path to lsregister: lsr='/System/Library/Frameworks/amework/Versions/A/Frameworks/amework/Versions/A/Support/lsregister If you have a large group of files that are opening in the wrong application even after changing the "Open With" setting, then resetting the Launch Services registry database should fix the problem.Īfter running lsregister to rescan the database or create a new UTI, run killall Finder to reload the Finder's “Open With” Menu, or just restart the machine. The Launch Service database controls the Finder's ' Open With' right click, contextual menu. Paths are searched for applications to register with the Launch Service database. Valid domains are " system", " local", " network" and " user".īe specified using only the first letter. dump Display full database contents after registration
Mac equivalent to lazy nezumi mod#
f force-update registration even if mod date is unchanged R Recursive directory scan, descending into packages and invisible directories r Recursive directory scan, do not recurse into packages or invisible directories lazy n Sleep for n seconds before registering/scanning convert Register apps found in older LS database files
lint Print information about plist errors while registering bundles
seed If database isn't seeded, scan default locations for applications and libraries to register kill Reset the Launch Services database before doing anything else
Lsregister is not on the system path so run it using the full path as shown in the examples below.