Repository navigation
readme: a mark above the title - #43
Merged
Merged
Conversation
The cursor fir: a text cursor for a trunk and shrinking rules for branches. It is the one candidate of the four that still reads as an idea at the size the page uses it, and it does not repeat the P that the title already carries. One file, drawn with its own rounded tile. A first attempt shipped two SVGs switched by prefers-color-scheme, and on the real page it served the near-black ink into a dark GitHub page, where the mark was invisible: a reader whose account theme and OS preference disagree gets the wrong half. The tile makes the mark visible on both themes from a single file, with no media query to trust. It lives inside the h1 rather than above it: awesome-lint allows exactly one heading, and a centred paragraph holding an image near the top of the file counts as a heading in its own right. awesome-lint 0, check_links 0 dead.
pAulseperformance
force-pushed
the
mark/cursor-fir
branch
from
November 17, 2026 05:28
d60f2b7 to
0b0fb0a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The cursor fir, 44px, inside the h1.
Why this mark. Of the four candidates it is the only one that still reads as an idea (a tree) at the size the page uses it, and the title already supplies the P, so a mark that repeats the letter spends its one job twice.
Why two files. A single stroke colour vanishes on white or on near-black.
<picture>withprefers-color-schemepicks the ink to match the reader's theme, and GitHub supports it.Why inside the h1. awesome-lint allows exactly one heading, and a centred paragraph holding an image at the top of the file counts as a heading in its own right, so a mark placed above the h1 would trip the rule.
awesome-lint0,check_links.py0 dead. Preview: https://github.com/pAulseperformance/awesome-pinescript/blob/mark/cursor-fir/README.md