krzyzanowskim

NSTextFinder documentation for the findBarContainer property says:

When the find bar is to be shown, NSTextFinder invokes showFindBarView: on the findBarContainer object, passing the view for the find bar, which it should display somewhere that is associated appropriately with the content being searched.

however that method is never ever called. There's little use of that method found on the Internet, and the only instance I found in Mozilla codebase, that suggest that maybe was called in the past. That would mean this is regression bug.

macOS 15.2 (24C101) Xcode 16.2 (16C5032a)

krzyzanowskim

import AsyncAlgorithms

final class AsyncChannelObserverToken {
    private let task: Task<Void, Error>
    fileprivate init(_ task: Task<Void, Error>) {
        self.task = task
    }

    func cancel() {
        if !task.isCancelled {

krzyzanowskim

#!/bin/sh

# SETUP
# 
# create executable file ~/.lessfilter with the content of this file
# chmod u+x ~/.lessfilter
#
# setup less by adding lines below to ~/.zshrc
# ```
# export LESSOPEN="| ~/.lessfilter %s"

krzyzanowskim

import Foundation

let dirURL = URL(filePath: "/Users/marcinkrzyzanowski/Downloads/filewrappertest.test")

// cleanup
try? FileManager.default.removeItem(at: URL(filePath: "/Users/marcinkrzyzanowski/Downloads/filewrappertest.test/COPY.png"))

let fw = try FileWrapper(url: dirURL)
// fw.fileWrappers // ["IMG_0736.png": <NSFileWrapper: 0x6000023a8420>]

krzyzanowskim

NSTextList is Equatable because NSObject is always Equatable, however if anyone expect that may compare two instances of NSTextList that is false. This is because NSTextList.isEqual() do return true value for equal instances. This situation makes impossible to eg. compare NSParagraphStyle instances with testLists property as it will always fail. This situation seems easy fixable and will significanlty improve testability of the codebases (eg. mine)

        do {
            let a = NSTextList(markerFormat: .disc, options: 0) // Equatable
            let b = NSTextList(markerFormat: .disc, options: 0) // Equatable
            let c = a == b        // false
            let co = a.isEqual(b) // false
        }

krzyzanowskim

UITextView does not call its marked text methods (setMarkedText, setAttributedMarkedText) for some languages, and does for other languages, but also for the same language it does not call on iOS, but does call on Catalyst (designed for iPad). Here's the example:

class TestView: UITextView {

    override func setMarkedText(_ markedText: String?, selectedRange: NSRange) {
        super.setMarkedText(markedText, selectedRange: selectedRange) // not called
    }

 override func setAttributedMarkedText(_ markedText: NSAttributedString?, selectedRange: NSRange) {

krzyzanowskim

Starting macOS 15/iOS 18 TextKit 2 extra line frame is more broken (height always been broken) than previously. The same code return different values when run on macOS 14/iOS 17 and macOS 15/iOS 18.

The problem is that extra line fragment (NSTextLineFragment) origin and size is incorrect. I sketch the problem with the code snippet below:

// Storage
let textContentManager = NSTextContentStorage()

// Layout

krzyzanowskim

[alias]
	# need llm CLI: https://llm.datasette.io/en/stable/
	# based on https://gist.github.com/karpathy/1dd0294ef9567971c1e4348a90d69285?permalink_comment_id=5167582#gistcomment-5167582
	commit-ai = "!f() { if [ -n \"$(git diff --cached)\" ]; then git commit -m \"$(git diff --cached | llm -m '4o-mini' 'Below is a diff of all staged changes, coming from the command:\\n```\\ngit diff --cached\\n```\\nPlease generate a concise, two-sentence, maximum 100 characteres commit message for these changes. Do not mention project name.')\"; else echo 'No changes to commit'; fi }; f"

krzyzanowskim

https://mastodon.social/@krzyzanowskim/113007925115490633

UITextView convenience initializer does not call designated initializer since iOS 16. The UITextView.init(usingTextLayoutManager:) that is a "convenience" initializer for the UITextView, does not call UITextView.init(frame:textContainer:) that is a designated initializer. This behavior, when the class interface traslated to Swift interface, breaks the Swift rules of object initialization. I believe that is also incorrect in Objective-C, although the compiler doesn't check that.

code snippet to reproduce:

final class CustomTextView: UITextView {

krzyzanowskim

the sample code published by Apple https://developer.apple.com/documentation/uikit/textkit/enriching_your_text_in_text_views show how List indicators does not render at all on macOS. This is regression as it used to work on macOS 13.

see attached video pf the EnrichingYourTextInTextViews Sample Code