Skip to main content

[BUG] b29 crashing on startup

Completed

Comments

6 comments

  • Todd Vanyo

    Following logging out and back in I'm able to relaunch nvU.

    0
  • Brett

    I've passed the crash report on to Fletcher for review. Thanks for the log.

    0
  • Fletcher Penney

    If it's fixed after logging out and logging back in, it *seems* to be a macOS issue, not an nvUltra issue.  The crash report indicated an issue with Apple's auto layout.  Nothing should change with nvUltra just from a log out, assuming everything is working properly with your computer.

     

    I don't do anything "super fancy" with the auto layout setup, and it's consistent every time to the best of my knowledge.  So, in theory, it should either work every time or break every time.  Of course, nothing is ever that simple.

     

    If there is a consistent issue, one thing to pay attention to is whether you have non-text files in the folder -- nvUltra swaps out the text editor for a quicklook preview.  To my knowledge, I worked out the kinks in this process, including when first opening a window with a non-text file selected and when rapidly scrolling through files.

     

    If anything changes with this, definitely let us know.

    0
  • Todd Vanyo

    Interesting that you bring up the non-text files. Do you mean files that aren't identified as public.text? Two things happened right before this crash and I need to recreate the situation to understand the impact.

    First, I deleted an "app" I had created to get `.tasks` files registered as public.text. I had done this to get nvU to recognize my `.tasks` files so I could edit them as needed. I see no need to open SublimeText for text files if I'm using nvU predominately now. My `.tasks` files are in taskpaper format.

    The second was that I opened a `.tasks` file in SublimeText and, using the Plaintasks package, marked an item as complete. I was trying to remember if the @due tag was retained along with the @done tag in Plaintasks.

    It was after doing these two things that I noticed I couldn't edit the `.tasks` files any longer with nvU, so I quit and attempted to restart nvU. The last file I was viewing was this `.tasks` file and it resided in the folder I was selecting when I relaunched nvU. 

    I suspect that deleting my fake app unregistered the `.tasks` file as public.text, but I want to recreate that and determine if it's true. It's possible that SublimeText did something to change the file attribute from public.text to public.data or something else (doubt this one). 

    Or I could go the easy way and just name the file `tasks.md` and move on with my life. But I hate knowing that something stupid like giving a file an extension like `.tasks` is causing some problem somewhere.

    0
  • Fletcher Penney

    Hmmm....  I will need to experiment with what might happen if the UTI changed "mid-stream"....  I *think* it would still be ok, but will need to verify that.  

    0
  • Todd Vanyo

    Just to follow up and close this, it looks like the action of deleting the dummy app I had created to let me register .tasks is what borked my setup.

    I've created another app, registered the .tasks as a plain.text UTI and I can continue editing the file in nvU even after modifying the file in ST3.

    0

Please sign in to leave a comment.

Powered by Zendesk