Raphael

Ah, my bad; these are `// MARK:` comments in our code. But why on earth are they included in these indices? They are far away from the declarations they accompany...

Alas, it does not seem possible to distinguish site types. I *want* the MARKs in class views (they make sense there). I only want to hide them in custom categories...

I won't consider manual approaches; any workaround needs to be scripted. Since I don't see a way to identify indices of custom-category section pages, this won't work. :/ Thanks, anyway.

Fully agreed. Without looking into the setup of ReSwift, I'd not gotten anywhere. In particular, the custom categories feature is not even mentioned!

A way to hide obsolete MARKs would be great. Example: ``` class Foo { // MARK: Doing Stuff /// ... public func foo() { ... } // MARK: Helpers ///...

Never mind, apparently Jazzy already does what I propose. :'D

@drekka Thanks for sharing! I already hack the CSS, but I for one don't want to hide *all* marks *everywhere*, but only those that don't make sense (cf. #780). FWIW,...

Definitely! This is basically expected if you come over from the Java world.

Thought: ```swift /// Makes objects of type `T` protocol Maker { associatedtype T /// Makes a `T` static func make(from: String) -> T } class Foo: Maker { typealias T...

Related: If `A: B` and `A` inherits `foo()` from `B`, `A.foo()` does not auto-link.