| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Make dots a little more salient on a light-background Vim.
|
| | |
|
| | |
|
| |
|
|
| |
Experimenting with a light background colorscheme.
|
| |
|
|
|
|
| |
Don't treat this as a section comment:
e8/call foo # -1 is negative
|
| | |
|
| |
|
|
| |
Colorize function names containing special characters like '?'.
|
| | |
|
| | |
|
| |
|
|
| |
Stop highlighting capitalized words in metadata as global variables.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
More tweaking of colors, as far as possible in 256-color terminal mode
that's almost entirely just for me, and beyond that in the generated html
that more people may look at. In the former I have to work with a limited
palette, while I'd like the latter to be more accessible for others.
Evolution of colors:
=== 1
.subxH1Comment { color: #00ffff; }
.subxH2Comment { color: #00afff; }
.subxComment { color: #00afff; }
.subxS1Comment { color: #0080ff; }
.subxS2Comment { color: #0040ff; }
=== 2
sed -i 's/^\.subxH1Comment.*/.subxH1Comment { color:#00ffff; }/' $1.html
sed -i 's/^\.subxH2Comment.*/.subxH2Comment { color:#00bbff; }/' $1.html
sed -i 's/^\.subxComment.*/.subxComment { color:#00bbff; }/' $1.html
sed -i 's/^\.subxS1Comment.*/.subxS1Comment { color:#0098ff; }/' $1.html
sed -i 's/^\.subxS2Comment.*/.subxS2Comment { color:#0070ff; }/' $1.html # slightly too dark
=== 3: http://www.perbang.dk/rgbgradient from start to end
sed -i 's/^\.subxH1Comment.*/.subxH1Comment { color:#00ffff; }/' $1.html
sed -i 's/^\.subxH2Comment.*/.subxH2Comment { color:#00ddff; }/' $1.html
sed -i 's/^\.subxComment.*/.subxComment { color:#00bbff; }/' $1.html
sed -i 's/^\.subxS1Comment.*/.subxS1Comment { color:#0099ff; }/' $1.html
sed -i 's/^\.subxS2Comment.*/.subxS2Comment { color:#0078ff; }/' $1.html
=== 4: drop down to 4 colors
sed -i 's/^\.subxH1Comment.*/.subxH1Comment { color:#00ffff; }/' $1.html
sed -i 's/^\.subxComment.*/.subxComment { color:#00d2ff; }/' $1.html
sed -i 's/^\.subxS1Comment.*/.subxS1Comment { color:#00a4ff; }/' $1.html
sed -i 's/^\.subxS2Comment.*/.subxS2Comment { color:#0078ff; }/' $1.html
=== 4: make final one just a little too dark
sed -i 's/^\.subxH1Comment.*/.subxH1Comment { color:#00ffff; }/' $1.html
sed -i 's/^\.subxComment.*/.subxComment { color:#00cfff; }/' $1.html
sed -i 's/^\.subxS1Comment.*/.subxS1Comment { color:#009fff; }/' $1.html
sed -i 's/^\.subxS2Comment.*/.subxS2Comment { color:#0070ff; }/' $1.html # slightly too dark
=== 5: make darkest shade a little less blue, just at the edge of too dark
sed -i 's/^\.subxH1Comment.*/.subxH1Comment { color:#00ffff; }/' $1.html
sed -i 's/^\.subxComment.*/.subxComment { color:#16ccff; }/' $1.html
sed -i 's/^\.subxS1Comment.*/.subxS1Comment { color:#2d99ff; }/' $1.html
sed -i 's/^\.subxS2Comment.*/.subxS2Comment { color:#4466ff; }/' $1.html # slightly too dark
=== 6: HSV gradient between the same endpoints
sed -i 's/^\.subxH1Comment.*/.subxH1Comment { color:#00ffff; }/' $1.html
sed -i 's/^\.subxComment.*/.subxComment { color:#16bfff; }/' $1.html
sed -i 's/^\.subxS1Comment.*/.subxS1Comment { color:#2d8cff; }/' $1.html
sed -i 's/^\.subxS2Comment.*/.subxS2Comment { color:#4466ff; }/' $1.html # slightly too dark
|
| |
|
|
| |
Another attempt at picking colors for the 5 different levels of comments.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Let's start highlighting all global variables in Red. Assembly programming
has a tendency to over-use them. They're a necessary evil, but we should
minimize the number of functions that access them.
|
| |
|
|
|
| |
Standardize on hyphens in all names.
And we'll use colons for namespacing labels in functions.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I'm going to continue using them for now, but I'm fairly certain now
that they're just a temporary device to help rapidly-prototype ideas.
The reason: there's just too many ways to abuse low-level features, and
it ends up taking too much code to disallow things soon after you allow
them.
New plan: stop trying to write checks, just treat them as temporary
conventions for now. Goal is now to just get the core sequence of passes
nailed down. Then we'll start reimplementing them from the ground up.
First implication of this new plan: ripping out most existing checks.
I'm still going to eventually build type checks. But no degenerate
checks for code just being too low-level.
(This decision is the outcome of a few days of noodling over Forth and
https://mastodon.social/@akkartik/100549913519614800.)
|
| |
|
|
|
|
|
|
|
| |
Targets you can jump to and ones you can call are conceptually disjoint
sets.
I'm highlighting these in Vim, but it's a pretty complex pattern.
Arguably errors shouldn't be highlighted. Only warnings that are easy to
be accidentally deployed.
|
| | |
|
| |
|
|
|
| |
As we climb the ladder of abstraction we'll gradually pull the ladder up
behind ourselves.
|
| | |
|
| |
|
|
| |
Syntax highlighting for dot leaders.
|
| | |
|
| | |
|
|
|
As we add high-level constructs we'll start labeling low-level
constructs as unsafe, and highlighting them in red in our editor.
|