| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
We're not using or rendering them yet.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
They don't have any semantics yet. We just ignore them for now.
|
| |
|
|
| |
Still highly experimental. I'm not persisting state yet.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
I'm still unclear on precisely what the experience should be here. We
probably don't need all of a version control system. The goal is just to
be able to answer the question, "what did I change recently that caused
things to break?"
For now let's just start with letting people see past versions.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
The problem: if ever I hit ctrl-e to go to the big picture view and then
hit Esc to go back to running the app, my terminal was messed up after
exiting the app.
Why did I even have this gunk? Perhaps it dates from the time when kilo
was emitting raw escape sequences rather than using ncurses.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
We only want to show most recent version of each binding.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
At least in short runs.
Encouraging that the problem was in a recent commit (5a63a5ca40 from
yesterday when I introduced version control).
Disabling Address Sanitizer again.
|
| |
|
|
|
|
| |
Many thanks to dirkf for https://github.com/antirez/kilo/pull/73!
However, teliva is still not ASan-clean.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
I'm starting to see some heap buffer overruns, which means we have too
much C code.
I noticed this because editing life.tlv no longer works after commit
5a63a5ca4. However, the offending heap overrun has been around long
before that. It's just been a silent bug until now.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
One old drawback now has a new look. Before, we loaded definitions in
order, so global definitions had to exist before other global
definitions that used them. See window and grid in life.tlv. Now we load
definitions in reverse order, so initialization needs to change. Worse,
if we update window, we need to edit grid just to fix the order.
This implies that we can't yet optimize away bindings where there are no
new changes.
|
| |
|
|
|
|
|
|
|
|
| |
Since everything is in my control there's no need to parameterize
include paths.
It's a struggle to get make to run when it should. Lying that something
is phony stops working when it's a dependency. Commands get
unnecessarily run. Just fucking run recursive makes directly in the
target that depends on them.
|
| | |
|
| |
|
|
| |
Now we're down to 1 real warning and 1 false positive.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Now we have 2 probably-valid warnings caused by my edits, and 1
false-positive.
|
| |
|
|
|
|
|
|
|
|
| |
I'd like to enable -Wextra as well, but that creates some false
positives.
I've at least made my changes clean w.r.t. -Wextra.
Now we have 4 remaining warnings with gcc 9.3 that seem genuine. Need to
fix those.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Adding -Wpedantic creates a new warning. Leaving it alone for now:
https://stackoverflow.com/questions/31526876/casting-when-using-dlsym
|
| |
|
|
|
|
| |
What in the world is up with the $MYCFLAGS convention in these Lua
makefiles? I don't know, but I'm going to leave it undisturbed as far as
possible.
|
| |
|
|
| |
cc and gcc are identical on my system. But why rely on that.
|
| | |
|
| |
|
|
| |
Hilariously, I wasn't linking against it in the first place.
|
| | |
|
| |
|
|
|
|
|
|
| |
Still extremely ugly:
- I've inlined all the namespaces under ssl, so you need to know that
context and config are related to ssl.
- luasec comes with its own copy of luasocket. I haven't deduped that
yet.
|
| |
|
|
|
| |
In the process we're starting to load almost all of luasocket by
default. And everything is working as expected, no unpleasant surprises.
|
| |
|
|
| |
Completely unmodified from upstream.
|