Pref setter8/30/2023 ![]() Therefore making it extremely difficult to handle if you want to get rid of private browsing for personal reasons. The real issue here is that Apple has decided to make safari essential to the OSX system (apparently) so it cannot be disabled, and also difficult to tweak protocols on. I did not ask how to enable parental controls, I asked how to disable private browsing. They all have lots of people, also very often VikingOSX giving non-solutions. Lastly I would point you to all of the other times it has been brought up in the apple support forums - Re: How do I disable private browsing on Safari 10.5.8? iMac, Re: Disable private browsing for children, Safari private browsing, Re: Disable Private Browsing in Safari on iMac, Safari 9: Can't disable private browsing etc. Also it doesn't really matter why one chooses not to have the function available, as that would not effect any solution given to disable it. The "solution" essentially was, don't use it. That's a nice way of looking at it I suppose but I highly doubt that. Do a quick Google search and you'll see many people, blogs, and discussions on forums as to how to do what I have described. just realize I am far from the only person with this question or desire. But some people would also like the option not to be there altogether.įor example - someone who has a *********** addiction may not want that option available to them because it disables extensions from blocking **** sites they wish not to view. ![]() Of course I or anyone else could simply not use it if we desire. The fact that you cannot think of one at all and simply narrow your response to - why don't you just not use it shows a lack of insight or possibly caring on your part. Now as to your response of, "how is it that you cannot simply avoid invoking this menu item?" There are many reasons to not want the option there altogether. I did it with google chrome via the institutions in this YouTube video - which used an app called pref setter to alter the code. There must be a way of doing so through plist protocols to turn the code to an integer value of 1 to hide it. See /usr/libexec/PlistBuddy -h for details.In my original post I described previous ways of doing so. is also capable of modifying Plist files from the command line (including, with limitations, importing from previously exported-to XML files).can be used to extract properties selectively using :-separated, case-sensitive property paths e.g., /usr/libexec/PlistBuddy -c 'print :favorites:ShowRemovable' ~/Library/Preferences/.If the plist has properties containing binary data, PlistBuddy will include it in raw form (by contrast, non-binary properties in the same file are printed properly). Alternative: Use /usr/libexec/PlistBuddy -c print, which outputs in JavaScript-object-literal- like format:Įxample: /usr/libexec/PlistBuddy -c print ~/Library/Preferences/.For viewing only: Use plutil -p, which prints the content of a property-list in JSON- like format (the format is meant for human consumption only).Įxample (append | open -tf to view output in a text editor): plutil -p ~/Library/Preferences/. ![]() Command-line options for viewing Plist files:
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |