| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
| |
up arrow doesn't seem to have the symmetric issue.
|
| |
|
|
| |
Found while reading https://www.gutenberg.org/ebooks/52091
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I'm now extracting the concern of computing
line.screen_line_starting_pos out of Text.draw. Earlier
I had to make sure I ran through the whole line to compute
screen_line_starting_pos, but that had the side-effect of updating
Screen_bottom1.pos as well with lines that had never been rendered.
In this process I hit my first bug due to an accidental global. It
doesn't show up in the patch because I accidentally deleted a local
declaration. (I thought I didn't need screen_line_starting_pos anymore,
deleted everywhere, then brought it back everywhere from the bottom of
the function up, but forgot to put back the very first occurrence.)
The amount of yoyoing this caused between App.draw and Text.draw, I very
much have spaghetti on my hands.
Accidental globals are _terrible_ in a program with tests. Cross test
contamination X-(
|
| |
|
|
| |
It wasn't screen-line aware. Now it is.
|
| | |
|
| |
|
|
| |
https://www.hogbaysoftware.com/posts/moby-dick-workout
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Why the fuck is this so fucking hard?
|
| | |
|
| | |
|
| |
|
|
|
| |
Setting up the test just right to test the thing I want to test was a
rube goldberg machine of constants.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I also really need to rethink how people debug my programs. My approach
of inserting and deleting print() takes a lot of commitment. I need my
old trace-based whitebox testing idea. However, in my past projects I
never did figure out a good framework for tweaking how verbose a trace
to emit.
Perhaps that's too many knobs. Perhaps we just need a way to run a
single test with the most verbose trace possible. Then it's just a
matter of having the trace tell a coherent story? But even if the trace
stays out of program output in that situation, it's still in the
programmer's face in the _code_. Ugh.
Current plan: ship program with maximum tests and zero commented-out
prints. If you want to debug, insert prints. This is better than
previous, text-mode, projects just by virtue of the stdout channel being
dedicated to debug stuff.
|
| | |
|
| | |
|
| |
|
|
| |
Drawings can't be drawn partially, which sometimes makes things jerky.
|
| |
|
|
|
|
| |
non-wrapping
Still lots wrong here.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
So far I've just changed how existing variables are organized, and put
some scaffolding in place for dealing with the new types. Next up:
rewriting the code for scrolling to something that feels more obviously
correct.
|
| |
|
|
| |
There's still an absence of affordance showing when you're in naming mode.
|
| |
|
|
|
| |
I'm still very much in the region where this is valuable sensor data.
This is a new domain.
|
| |
|
|
| |
keeping cursor on screen
|
| | |
|
| | |
|
| |
|
|
|
|
| |
of a line
But we still have work to do for cursor up/down.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Still lots of signs it's all messed up, but I can't be sure until I
bring all the other keyboard shortcuts in sync.
I just need a better data structure that simplifies the logic. Perhaps
talk in terms of screen lines. In which case:
We'll need to convert lines to screen lines at some point.
We'll need to fix up screen lines when inserting and deleting
characters.
|
| |
|
|
|
| |
I've been only thinking about up arrow when cursor is at top of screen.
Hopefully this is better.
|
| | |
|
| |
|
|
| |
Looks pretty clean.
|
| |
|
|
|
|
|
| |
I'd wrapped currx in two conditionals, and not noticed that it gets
reclaimed within the other.
The hint is clearly more work than it's worth. Just take it out.
|
| |
|
|
|
| |
I'm not setting these yet. Rendering seems to be working after manually
setting them.
|
| | |
|
| | |
|
| |
|
|
| |
We'll start using this in cursor up/down motions.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|