After that change during boot chosen default system will be opened without going through GRUB menu.\
Note
You can still open GRUB menu by pressing Shift
key while booting.
// -- Usage | |
struct Content: View { | |
@State var open = false | |
@State var popoverSize = CGSize(width: 300, height: 300) | |
var body: some View { | |
WithPopover( | |
showPopover: $open, | |
popoverSize: popoverSize, |
import UIKit | |
extension UIApplication { | |
// MARK: Public | |
func isRunningInTestFlightEnvironment() -> Bool { | |
if isSimulator() { | |
return false | |
} else { | |
if isAppStoreReceiptSandbox() && !hasEmbeddedMobileProvision() { |
#!/bin/bash | |
# This assumes that the ~6GB mojave installer is in the /Applications folder. | |
# If it's not, just open the App Store, search Mojave, and you can download the installer file from there. | |
hdiutil create -o /tmp/mojave.cdr -size 6g -layout SPUD -fs HFS+J | |
hdiutil attach /tmp/mojave.cdr.dmg -noverify -mountpoint /Volumes/install_mojave | |
sudo /Applications/Install\ macOS\ mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/install_mojave | |
mv /tmp/mojave.cdr.dmg ~/Desktop/InstallSystem.dmg | |
hdiutil detach /Volumes/Install\ macOS\ mojave |
Let's say you receive an app (e.g. MyApp.ipa) from another developer, and you want to be able to install and run it on your devices (by using ideviceinstaller, for example).
Or your certificates and provision profiles have expired and you want to provide a new build to your clients without having to make a new build on the latest XCode or iOS SDK.
The first step is to attain a Provisioning Profile which includes all of the devices you wish to install and run on. Ensure that the profile contains a certificate that you have installed in your Keychain Access (e.g. iPhone Developer: Some Body (XXXXXXXXXX) ). Download the profile (MyProfile.mobileprovision) so you can replace the profile embedded in the app.
Bash is the JavaScript of systems programming. Although in some cases it's better to use a systems language like C or Go, Bash is an ideal systems language for smaller POSIX-oriented or command line tasks. Here's three quick reasons why:
This document is how I write Bash and how I'd like collaborators to write Bash with me in my open source projects. It's based on a lot of experience and time collecting best practices. Most of them come from these two articles, but here integrated, slightly modified, and focusing on the most bang for buck items. Plus some ne
# Customize BASH PS1 prompt to show current GIT repository and branch. | |
# by Mike Stewart - http://MediaDoneRight.com | |
# SETUP CONSTANTS | |
# Bunch-o-predefined colors. Makes reading code easier than escape sequences. | |
# I don't remember where I found this. o_O | |
# Reset | |
Color_Off="\[\033[0m\]" # Text Reset |
sudo find /private/var/folders/ -name com.apple.dock.iconcache -exec rm {} \; |
(from :http://www.entropy.ch/blog/Developer/2010/04/15/Git-diff-for-Localizable-strings-Files.html) | |
First, add this to the project’s .git/info/attributes file: | |
+ | |
*.strings diff=localizablestrings | |
(Unfortunately you do have to add it to every project, there doesn’t seem to be a global attributes configuration file) | |
Second, add this to your ~/.gitconfig file: |