Beware, this has the potential of making you go crazy! For instance, you may choose “c” as your Hyper, if it is pressed for more than 500ms. Technically, any key will do as long as it does not intervene with your daily operations. ![]() Nothing is free, to gain a new modifier key you have to sacrifice one. But in the end, it will save you more time and help you get and stay in flow. The setup will take a some minutes, getting used to these shortcuts will probably take a few hours to days. Once you get the hang of it, you can never let go. You’ll develop micro-habits that will increase your productivity and control. Essentially, it is a framework for scripting macOS.īy combining these two powerful tools, you’ll be able to customize your setup in a way you never thought possible. It exposes macOS APIs for applications, windows, screens, filesystem, events, etc. Imagine control+c like custom keybindings working consistently and seamlessly in every application. It lets you create 2-key global shortcuts without conflict. The Hyper key is a “new” global keyboard modifier. ![]() The recipe you’ll find below rests on two foundations. These few simple tricks will make your life easier and more productive, trust me. In this post, you’ll find the distilled results of my efforts. This encounter inspired me to start customizing my workflows. He was a “modern magician.” As life has it, he is a classical magician as well. His secret? Shortcuts, custom IDE extensions, and practice, lots of it. His moves were elegant and effortless he seemed to be one with the machine. He was conjuring up classes, navigating the code, and refactoring at a speed I never saw before. He seemed slow and thoughtful with his gestures, but the world changed so fast, I had a hard time following. I have been programming for a while now and met quite a few “wizards.” One day, I was pairing with a colleague, and it completely blew my mind. ![]() Clarke who drove this parallel home by one of his laws.Īny sufficiently advanced technology is indistinguishable from magic. Push a few buttons, make some gestures on a trackpad and a whole new world comes alive. It was all a fantasy until I discovered programming and computers in general. Utter a few words, wave your hands around and BOOM the world changes at your will. When seeing a wizard performing magic, it seems like anyone could do it. I was never a believer, but I fell in love with the concept of humans conjuring unbelievable realities by saying words and making simple gestures. Today, in Xcode 13.How to become a modern magician? - productivity tips for devs on macOS Now for the other packages, check their own dependencies and make sure these are equal. In my case, that was CustomerKit, version "11.0.1 - Next Major". If you get it, select your project in the left navigation, select the project again in the middle pane, select the Package Dependencies and look up the version of the dependency. The fact that the error twice mentions "root depends on xxx", is thus wrong. So what this error message actually means, is: you added a local package, and both the main project and your local package rely on the same package (customerkit in this case), but they require different versions. The error was confusing to me, because it specifies that root (which means the current project, I assume) depends on both version 11.x and 13.x which is obviously not the case. The project had built correctly, then I wanted to edit code in a package so I added it as a local package. Today, Xcode gave me the following error: Dependencies could not be resolved because root depends on 'customerkit' 13.0.0.<14.0.0 and root depends on 'customerkit' 11.0.0.<12.0.0. But it'll probably improve in the coming versions. I'm not yet happy with the way Xcode handles Swift Packages, it feels unreliable in the current version. That error reads: "Package.resolved file is corrupted or malformed fix or delete the file to continue: unsupported schema version 2". But we never opened the project in any Xcode version higher than 13.2.1. From that 13.3 version and upwards, Xcode will upgrade the Package.resolved file to a new v2 format. Note that this is NOT the same as the error that Xcode 13.2.1 or lower shows when someone else opened it with 13.3 or higher. So this may not actually be the final solution for you. In our case, Xcode actually downgraded some dependant package in (minor) version. Just a tip for when you encounter this behavior. Then started Xcode again and opened the workspace: it built. ![]() The problem was fixed by manually removing the file, doing a "clean build folder", then quit Xcode and the simulator. That is exactly after a successful pull request, so the project has built successfully before. Today Xcode gave me the error "Package.resolved file is corrupted or malformed fix or delete the file to continue: malformed" when opening and running an xcworkspace with a Swift package and a sample app.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |