Skip to main content

Folders open in nvUltra instead of Finder

Completed

Comments

28 comments

  • Fletcher Penney

    Hmmmm...  Interesting.

     

    Technically, nvUltra has to register as handling documents with the UTI `public.folder`.  I've never seen it "take over" as the default handler for that UTI, but perhaps it is possible.  Doing "Get Info" the Finder for a file allows you to check and modify the default application for that UTI.  But it doesn't seem to work for folders (which makes sense)

    Sadly, the process by which macOS decides which application "wins" for a particular UTI is apparently a hidden algorithm.  If you can't manually set a default, I guess you can try removing nvUltra, rebooting your computer, and then reinstalling nvUltra and seeing what happens....

    Input from anyone else with tips here is welcome.

     

    0
  • Howard Dinin

    Having the exact same problem. Discovered when I tried using the Applications folder access from the Dock and requested "Open in Finder" [and later trials showed this affected the "Downloads" folder Dock icon as well).
    The appearance of the window conforms to the settings for nvUltra (color, view preferences, etc.) and the Finder remains in nvUltra, that is, the nvUltra menu remains in the menu bar. This is occurring on a device running Mojave 10.14.6. I have not tried other devices running more current OS versions. I have a screen shot if that will help. It's not a great handicap, because I rarely use this Dock/Finder function (to open and view contents of desktop folders), but if I get a chance, I will try removing and then re-installing nvUltra to see what happens.

    0
  • Howard Dinin

    Tried this on another device, running under the latest version of Big Sur (v.11.6), and everything is fine with regard to this anomaly... at least for the Applications and Downloads folders.

    0
  • Stuart Matthew

    Having this problem on Mojave 10.14.6 as well. Encountered it when selecting "Open Downloads" from the Downloads Dock icon.

    Howard, did removing and reinstalling nvUltra change this behaviour on your Mojave install?

    0
  • Howard Dinin

    Update:

    Sorry Stuart, I've not yet had a chance to try re-installing nvUltra on the Mojave machine.

    I have tested yet a third device, also running Big Sur (v.11.5), and there is no problem.

    Will report any results of attempting the re-installation.

    Howard

    0
  • Fletcher Penney

    If you are having this trouble, can you try this in Terminal -- `defaults read com.apple.LaunchServices/com.apple.launchservices.secure` and look for the section that includes nvUltra?

     

    If I understand the problem correctly, you *should* see a section (approximately 7 lines including wrapping braces) that includes nvUltra.  I do not see one, and do not have this problem.

    Can anyone confirm?

    0
  • Fletcher Penney

    Alternatively, look for `public.folder`

    0
  • Howard Dinin

    Tried the terminal command line suggested: no sign either of "nvUltra" or of "public.folder," in any bracketed sub-section, though problem persists. Will try deletion of nvUltra app and re-installation...

    0
  • Stuart Matthew

    Thank you both.

    Same result for me from suggested Terminal command - a listing of LSHandlers with no 'nvUltra' or 'public.folder' listed

    0
  • Howard Dinin

    I removed nvUltra app (the 09.01.20.19 build of the current beta) along with all associated files AppCleaner could find. I re-installed that same, latest, version on this device freshly downloaded from the forum link.

    Sorry to report, the problem persists.

    Strangely, what did persist were all the nvUltra preferences settings of the deleted version. I could have sworn that the file 'com.multimarkdown.nvUltra.plist' was also deleted with the purge. I assumed this was where the preferences were stored. But, even with a newly generated .plist file, the settings were, as I say, intact. Not pretending to imagine, never mind know, if this is related to the problem, which seems OS specific.

    0
  • Stuart Matthew

    I uninstalled as well and tested selecting "Open Downloads" from the Downloads Dock icon again which returned to normal behaviour of opening a Finder window.

    Reinstalling nvUltra reintroduced the issue.

    0
  • Howard Dinin

    Smart thinking Stuart. I didn't think to try opening a folder from the dock shortcuts before re-installing.

    But the result seems to be the same.

    0
  • Fletcher Penney

    Can either of you create a new user account and see if the problem occurs?

    In the past some third party utilities have caused some strange behavior until realizing they were in use.

    0
  • Fletcher Penney

    PS> Thanks!!!

    0
  • Stuart Matthew

    Not a new account but I switched to another existing account - no nvUltra in the Dock. "Open Downloads" from the Dock icon opened a Finder window. 

    Went to Applications folder and launched nvUltra. Tried "Open Downloads" again and the folder tried to open in nvUltra again. 

    Apologies, I'll have to call it a night. 2:08 am here. Thanks for your help - I'll check in again tomorrow.

    0
  • Tully Hansen

    Just came to see if anyone else experiencing the same issue – don't have a fix or much time for testing right now, but I'm recently (?) seeing the same behaviour (folders opening in nvUltra) when hitting Return on a folder in Spotlight search results.

    Similarly not seeing "nvUltra" or "public.folder" in output of defaults read com.apple.LaunchServices/com.apple.launchservices.secure.

    Mojave 10.14.6 (18G9216), nvUltra 1.0.0 (2021.09.01.20.19).

    0
  • Howard Dinin

    I found some time to create a new user. I did so. The new user was set up to have no administrator privileges, but with its own password.

    I opened nvUltra and was welcomed to the beta version with a fresh welcome screen, which I scrolled through.

    I set up a new folder in the new user's documents folder for notes to be created in nvUltra.

    I created one note. I then attempted to open (from the dock icons) the "Applications" folder, which I had added, and from the "Downloads" folder, which the system had placed in the dock by default.

    With each, the new window opened, but within nvUltra.

    That was the extent of my experimenting.

    I'm glad to help out, but in this instance, I was a little less glad. Once I had logged out and logged back in as the sole user I've always been, I discovered that the process of testing nvUltra and its impact on folder and file handling in Finder meant, as I performed it (creating a new user and within the new user space, creating a "new" installation of nvUltra beta by that user), nvUltra had created a whole new preferences file, which I would have expected.

    What I didn't expect was that on returning to the default primary user environment (me, that is) that nvUltra, when booted up, would act like a completely new installation of itself, with a new fresh "Welcome" to beta screen, and all previous preferences settings wiped out. I've done a partial restoration – all I have time for at the moment – and I'll return to this task and hope nothing's been lost in terms of how I have come to be familar and comfortable with the nvUltra interface. It reset Everything. Starting with the "paid app"/"free app" setting in General settings. Setting a default font for the editing window was particularly troublesome, far more complicated (and listing some "default" fonts whose names I had never seen in my life, e.g., "Atkinson Hyperlegible" and "Taviraj"), and took some fiddling to return to my original settings (which did not readily link with the "Fonts" management window that opens in preferences when you click on "Other"; nvUltra did not respond to the settings in this window, in terms of entering the settings, mainly font name and font size).

    My only additional step, at this point, was to delete this new user and its home folder.

    If there's something new to try to help diagnose this behavior, I am still game to try, but especially if it creates no "new" work. I understand the compact I agreed to when signing on to use beta software, but, in the hopes of being very close to a first "gold" release, I have perhaps instilled in myself more confidence than the current state of the app warrants. That said, I hope these notes have been helpful.

    0
  • Fletcher Penney

    Howard Dinin

     

    1. Thanks for trying a new user account.  Removing as many variables as possible is sometimes key to figuring out what is going on, especially when a problem is occurring for what seems to be a persistent but small proportion of users.  Third party utilities are one of those things, and a new user account can exclude many of them (though not any that are installed at the "system" level).  Thanks for checking this.

     

    2. I can't explain what happened to your primary user preferences.  nvUltra does not have any special permissions to reach "across" user accounts and change preferences, which are stored in each user's Library folder separately (and therefore owned by different user accounts and permissions within the macOS file system).  So nvUltra run by one user doesn't have permission to modify a separate user's home directory.  And if nvUltra managed to find some "wormhole" that allowed it to access preferences in a separate user's home directory, then I would expect that the previous settings would have appeared rather than a brand new empty set (nvUltra does not have a "wipe all current preferences" feature). 

     

    3. As for fonts, there was an error where the built-in fonts (including those that you named) were not embedded within the app bundle as intended.  This is now fixed for the next release (thanks for pointing this out).  But that said, any changes made in the "Fonts" dialog when you select "Other..." should be immediately reflected in open windows, unless you are using a theme that overrides the font/size preferences.  Selecting a font in the "Fonts" dialog should also immediately update the "Default font" and "Default font size" text fields in the appearance preferences as well.  This still works appropriately for me, and I have not heard of anyone else having issues with this. Similarly, typing a name in the "Default font" field should work once you hit return, assuming you typed the proper name of course.  Using the Fonts dialog is more reliable, but experts can certainly modify those text fields directly if they are confident they know what to enter.  (Remember that the actual names of fonts, the file names of fonts, and the display names of fonts are not always the same....)

     

    You are not the only user reporting issues with folders opening in nvUltra instead of the Finder, as evidenced by this thread.  But I have not heard of anyone else with the other issues you describe.  I will throw out there that on more than one occasion, users have experienced unusual behavior in applications that turned out to be related to corruptions in their underlying system (including myself.)  It seems that this is most common when a computer's system is updated "in-place" multiple times (e.g. 10.12->10.13->10.14 (and the various point releases in between.)  This happened to my wife when an issue with searchlight occurred that caused crashes in a variety of seemingly unrelated situations and applications.  When we turned off indexing for her home folder, all of these crashes immediately went away.  It was bizarre, to say the least.  When I hang onto a given machine for more than a few years, I try to wipe the drive and start fresh periodically to prevent such problems.  "Back in the day", installing a fresh copy of the system was an option when updating, but that seems to no longer be the case.  That may not be what is happening to your computer, but I have been burned before by not mentioning it when I think of it.

     

    Thanks again for testing a new user account.  I'm still trying to track down exactly what is happening here.  It *seems* to be a straightforward issue of macOS thinking nvUltra should be the default app for folders, rather than the Finder.  But I am unable to a) verify that is happening, b) come up with a way to fix it.  And this is complicated by the fact that I have never seen this happen, despite building and installing more copies of nvUltra than anyone else on the planet....  ;)

    0
  • Fletcher Penney

    furgere -- what version of macOS are you using?

    0
  • Howard Dinin

    Fletcher, your Point 2 in your comprehensive message in response (for all of which, thanks) was baffling to me also, though after reading through this entire thread, I think I have a hypothesis. I think I "wiped" the existing preferences file when I mechanically removed nvUltra.app and supporting files (with the assistance of AppCleaner). I then re-installed nvUltra, but I had not, in the interim, restarted or cold booted the device (it's an "ancient" Mac Pro 5,1; hence the need to run Mojave and nothing more recent; so it's a real pain in the ass sometimes to restart this beast). I am assuming the original "settings" for nvUltra somehow still resided in memory, without being displaced when the replacement file was booted up. It was after logging out of the machine, prior to logging in as a new "test" user, that the new install of nvUltra wrote in the space in the Preferences folder, after I logged back in as primary user, of the Library of the primary user a "blank" .plist container, and, presumably unless it's the same location a new container for whatever file holds the "Welcome screen" which I saw after logging out of the test user and logging back in as primary user. It's also possible, because it's true, that I have no idea what I'm talking about. But it's the only way, with my limited knowledge of how the phenomenon I described of "losing" my preferences could have occurred.

    0
  • Fletcher Penney

    Howard Dinin -- I don't use AppCleaner, but presumably if you used it then it would have removed the defaults file.  More recent versions of macOS (I don't remember exactly when) store the "actual" defaults in a database somewhere, and the file in the user's library folder "sort of" represents this data.  It may have been that AppCleaner deleted the file, but that this didn't actually trigger an update of the defaults database until later, which made it seem like the preferences were deleted at a different time than they were.  This makes sense.

     

    I discovered this years ago when modifying the plist text files in the Library preferences folder no longer changed app behavior reliably.  Using the `defaults` command in the terminal is now the way to manually tweak preferences, rather than editing text files.  This was quite confusing until I figured out what was going on....

    0
  • Fletcher Penney

    I think I found the issue with folders opening in nvUltra instead of Finder.  Should be fixed in next release.

     

    0
  • Howard Dinin

    yay

    0
  • Fletcher Penney

    Should be fixed in today's release.  Let us know if you still have trouble.

    1
  • Howard Dinin

    Whatever other goodies you added or fixed in today's release, you DID, in fact, fix the default folder problem... Works as it's supposed to, once again, in Mojave... Thank you for this.

    0
  • Fletcher Penney

    A few goodies, and even more for the next release (coming soon).

    1
  • Fletcher Penney

    (And glad to hear it's fixed for you!)

    1
  • Vito Traino

    Thanks for this fix!

    0

Please sign in to leave a comment.

Powered by Zendesk