Jake Petroules
Jake Petroules
To achieve strict RFC 3986 conformance (specifically, '+' in query strings is a LITERAL '+' and not a placeholder for ' ' as per the W3C's URL recommendations, the following...
Although OpenConnect behaves as a menu bar application on macOS, it still shows an icon in the Dock. This is undesired. To properly mark the app as a menu bar...
The menu bar lists the name as "OpenConnect-GUI" and the actual bundle and executable name is "openconnect-gui". It would be more "Mac-like" to call both of these as "OpenConnect". Even...
OpenConnect releases are distributed via GitHub Releases, it seems. OpenConnect should use [Sparkle](/sparkle-project/Sparkle) on macOS to automatically update itself. The appcast file required by Sparkle can be hosted on the...
On Windows, _dup2 is [documented](https://learn.microsoft.com/en-us/cpp/c-runtime-library/reference/dup-dup2) to return 0 to indicate success, in contrast to POSIX's dup2, which returns the new file descriptor. Should we change the Windows syscall adapter to...
Consider the following (tested with v1.3.1 tag): ```swift let fp = FilePath("Sources/E:\\source") print(fp.isAbsolute) // false print(fp.isRelative) // true print(fp.root) // nil print(Array(fp.components)) // ["Sources", "E:", "source"] print(FilePath("Sources").appending(fp.components)) // SystemPackage/FilePathParsing.swift:351: Assertion...
Consider the following program: ```swift import Foundation print(FileManager.default.currentDirectoryPath) let path = NSTemporaryDirectory() + "/" + UUID().uuidString try FileManager.default.createDirectory(atPath: path, withIntermediateDirectories: true) _ = FileManager.default.changeCurrentDirectoryPath(path) print(FileManager.default.currentDirectoryPath) try FileManager.default.removeItem(atPath: path) print(FileManager.default.currentDirectoryPath) ```...
The following code, if compiled as an x86_64 process and run on an arm64 system, will claim that the command shell binary is not executable. This is because GetBinaryTypeW returns...
utimensat has nanosecond precision, while utimes only has microsecond precision. At least APFS should be able to take advantage of the elevated precision.
Should FileManager.attributesOfItem(atPath:) and similar APIs expose Alternate Data Streams on Windows? They're somewhat logically equivalent to extended attributes on Unix-y platforms, so it might make sense.