chockenberry

#!/bin/sh

# usage:
#	ql /tmp/file.jpg
#	cat /tmp/file.jpg | ql
#	cal -h | ql

if [ -z "$*" ]; then
	cat > /tmp/ql.stdin
	mime_type=$(file --brief --mime-type /tmp/ql.stdin)

onmyway133

// swift-interface-format-version: 1.0
// swift-compiler-version: Apple Swift version 5.7 (swiftlang-5.7.0.113.10 clang-1400.0.16.2)
// swift-module-flags: -target arm64-apple-ios16.0 -enable-objc-interop -enable-library-evolution -swift-version 5 -enforce-exclusivity=checked -Osize -library-level api -library-level api -module-name SwiftUI
// swift-module-flags-ignorable: -user-module-version 4.0.66.3.102
import Accessibility
import Combine
import CoreData
import CoreFoundation
@_exported import CoreGraphics
@_exported import CoreTransferable

rileytestut

import Foundation

// Export running app as .ipa, then return path to exported file.
// Returns String because app crashes when returning URL from async function for some reason...
func exportIPA() async throws -> String
{
    // Path to app bundle
    let bundleURL = Bundle.main.bundleURL
    
    // Create Payload/ directory

ChristopherA

Brew Bundle Brewfile Tips

Copyright & License

Unless otherwise noted (either in this file or in a file's copyright section) the contents of this gist are Copyright ©️2020 by Christopher Allen, and are shared under spdx:Creative Commons Attribution Share Alike 4.0 International (CC-BY-SA-4.) open-source license.

Sponsor

If you more tips and advice like these, you can become a monthly patron on my GitHub Sponsor Page for as little as $5 a month; and your contributions will be multipled, as GitHub is matching the first $5,000! This gist is all about Homebrew, so if you like it you can support it by donating to them or becoming one of their Github Sponsors.

myell0w

/// Used to identify traits of the current UI Environment - especially useful for cross-platform code
public struct MNCUITraits: Withable {

    /// Does *not* identify the device type, but the idiom of the layout to apply
    /// This means that e.g. on iPad the layoutIdiom can be `.phone`, if run in Split Screen or SlideOver
    public enum LayoutIdiom {
        case phone(hasRoundCorners: Bool)
        case pad(hasRoundCorners: Bool)
        case mac
    }

IsaacXen

WWDC                                2006  2007  2008  2009
2010 2011 2012 2013 2014 

4np

How to use a .xcconfig file and a .plist file with SPM

Worth a read for some more context.

Create a Package.xcconfig file

Create the file in the root of the project (where your Package.swift file lives as well), and use the following contents:

/// Package.xcconfig

hyuni

#!/bin/bash
# usage: get [ RESOLUTION [ YEAR [ IDS... ] ] ]

resolution=${1:-SD}
year=${2:-2015}
shift
shift
ids=$*

RESOLUTION=$(echo $resolution | tr '[:lower:]' '[:upper:]')

kevinelliott

To support my open-source work, consider adding me on Patreon.

macOS 10.14 Mojave Mostly-Automated Setup

An easy to refer to document for regularly setting up macOS 10.14 Mojave.

Controversy

The topic of recipe-based frequent fresh reinstalls of macOS is a controversial issue. Some people are against reinstalling macOS, citing that they have never had an issue with Apple provided upgrade installs.

tclementdev

libdispatch efficiency tips

The libdispatch is one of the most misused API due to the way it was presented to us when it was introduced and for many years after that, and due to the confusing documentation and API. This page is a compilation of important things to know if you're going to use this library. Many references are available at the end of this document pointing to comments from Apple's very own libdispatch maintainer (Pierre Habouzit).

My take-aways are:

• You should create very few, long-lived, well-defined queues. These queues should be seen as execution contexts in your program (gui, background work, ...) that benefit from executing in parallel. An important thing to note is that if these queues are all active at once, you will get as many threads running. In most apps, you probably do not need to create more than 3 or 4 queues.

• Go serial first, and as you find performance bottle necks, measure why, and if concurrency helps, apply with care, always validating under system pressure. Reuse