Scoping the “find-in-project” search results (say to only return *.js files) requires creating a new search scope. The Mac-ness of Nova is very, very strong. That said, it seems to return good search results. My only issue so far is that it seems get stuck on “Indexing Files…” for me quite a bit (or feels stuck because it gets the ol’ fan spinning). “Find-in-project” is something I do at least a dozen times a day, so that’s something that needs to work tremendously well for me. For example, I don’t need a plugin to make my indendations all rainbow-ified because they already are! But notice the JSX isn’t particularly well highlighted even though it’s on the right syntax. It would be a bonus to me if the default behavior of Nova was so good off the shelf that it didn’t need as many third-party tweaks (aside from the two biggies I already mentioned).
#CODA 2 PROJECT FILE CODE#
They all add some little nicety to VS Code for me specifically.
I have nearly 30 VS Code extensions activated. I was able to map all the things I’m used to, like setting Command-T to “Open Quickly” which is like the “Go to file…” setup in VS Code. It does have all the extra fancy things Emmet can do though, which you can map to whatever keys you want. The default expansion for Emmet is Ctrl-E though, and it doesn’t work with Tab expansion (as far as I can tell), which isn’t my favorite. Fortunately, they are some of the top extensions. If I couldn’t have those, I’d be out for sure. I really, really like Prettier and Emmet.
Like a lot of other people, I’m on the VS Code train. I got a little discount as it went live, so I bought it and am using it here and there. I played with some of the betas as they were building it. It’s like “Coda 3” except this was such a major re-write that they gave it a whole new name. It’s just a suggestion and pointer to the necessary files to help improve your backup solution.Nova is a new (vehemently macOS-only) code editor from Panic, the folks behind Coda. Select your original keychain file from your backup and hit OKĭisclaimer: I take no responsibility if this process does not work for you and all backups are lost.Click the + button to add another keychain.Open the Keychain Access application in the Applications/Utilities.The next time you need to recreate all your Coda sites (and recover all those Keychain passwords), simply copy these files back to your machine in the same locations with a few tweaks to recover the passwords: A quick Google found that all your Keychain passwords are stored in another local file: ~/Library/Keychains/login.keychainĪgain, alias the file and drop it in your Dropbox. Leanda also asked how FTP details were saved. I’ve now created an alias of the file and placed it in my Dropbox so all changes are automatically cloned online.
#CODA 2 PROJECT FILE FULL#
It turns out, it’s not too complicated.Īll the Coda Sites and preferences are stored in a single place on your Mac (replace ~/ with /Users/(your username)/ for the full path): ~/Library/Preferences/ Whilst preparing for a machine refresh, I realised there must be a simple way of automatically creating a backup of all the Site details stored in Coda without having to recreate them on the other side. Personally, I find the site management and native SVN integration key to my rapid development process, whilst maintaining a user-friendly experience with the clean Cocoa interface and Clips library.
#CODA 2 PROJECT FILE SOFTWARE#
Many web developers I know are now using the fantastic code editor software from Panic, Coda.