Closed mauricioszabo closed 1 month ago
Does this need some more input from other folks? Is this ready for wider use? Would it be welcome for someone to grab a build of this branch and test a few things?
I don't mean to leave this PR open without responding to it, so seeing if I can be of help.
Yeah, I think the:
Some migration to the SQL version (so we don't lose things)
Can be done in a different branch :)
Translating: sure, let's merge it if it's ok with more people
I think I should test-drive this before moving to merge it.
Anything in particular I should try? Just loading up a bunch of windows with lots of tabs, and shutting down then reopening and reloading Pulsar a bunch of times? Open and close a lot of tabs, stuff like that?
Would there be anything in particular that would best show it is working?
Yes, @DeeDeeG, that's right. Don't forget to toggle the option in the config.
Although, I've been test-driving this for a while, and so far, I found no problems...
I found an issue using this branch's binary on macOS.
Pulsar.app
. Don't copy to /Applications
folder, just leave it where it is.package.json
file?"Maybe Pulsar is looking for core Pulsar files in the wrong place, at the old stale "AppTranslocation" path from previous launch? (AppTranslocation dir is different every launch as a security measure for .app
s launched from outside the /Applications
dir, I think?
These steps to reproduce do not have the issue on Pulsar Rolling 115, and I think the issue doesn't happen if the "Untitled" file doesn't have any semicolons typed in it. So, maybe it's just a matter of escaping some semicolons, sanitizing inputs? Hmmm.
Seems like a sqlite.js
NPM module error, really... maybe it's not finding the right directory for the SQLite binary...
Will fix https://github.com/pulsar-edit/pulsar/issues/531
Needs: