about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 1793 - rudimentary sandboxing for scenarios in the environmentKartik K. Agaram2015-07-152-2/+11
|
* 1792 - better semantics for ctrl-kKartik K. Agaram2015-07-151-3/+122
| | | | More evidence that the choice of 'before-cursor' was inspired.
* 1791 - delete to start/end of lineKartik K. Agaram2015-07-151-0/+166
|
* 1790 - move to end of lineKartik K. Agaram2015-07-151-0/+145
|
* 1789 - move to start of line with home/ctrl-aKartik K. Agaram2015-07-151-2/+133
|
* 1788Kartik K. Agaram2015-07-151-1/+3
|
* 1787 - clear warnings between runsKartik K. Agaram2015-07-152-29/+39
|
* 1786 - render only the side that changedKartik K. Agaram2015-07-151-8/+33
|
* 1785Kartik K. Agaram2015-07-151-5/+23
|
* 1784 - start making render more efficientKartik K. Agaram2015-07-151-1/+0
| | | | | We stopped rendering just the widget under focus when we switched away from the simplistic list of editors. Need to bring that back.
* 1783 - stable if sluggish on caleb's 512MB serverKartik K. Agaram2015-07-142-8/+45
| | | | | Profiling shows the bulk of time is spent in read_memory, canonize, absolutize. But I'm not sure how to optimize those places.
* 1782 - stop tracing anything but warnings inside editKartik K. Agaram2015-07-143-4/+7
| | | | | | | | | Speeds up edit.mu tests by 10x, and shrinks memory usage by 100x. We need a more efficient implementation of traces, but we can keep going for now. We didn't really need to reclaim memory just yet, after all. Mu is pretty memory-efficient.
* 1781 - the hog is Trace_stream, not MemoryKartik K. Agaram2015-07-142-0/+19
| | | | | I keep forgetting about it. Until, that is, I run gprof. Even if I think I need a memory profile, a cpu profile is a pretty good proxy.
* 1780 - now we always reclaim local scopesKartik K. Agaram2015-07-1317-123/+168
| | | | | | But still no difference in either memory footprint or in running time. This will teach me -- for the umpteenth time -- to optimize before measuring.
* 1779Kartik K. Agaram2015-07-131-0/+86
| | | | | | Now we can reclaim allocated space. But the API's suspect. I still want to provide some sort of tree of allocations. For now we'll use this only to reclaim default-spaces. That's next.
* 1778Kartik K. Agaram2015-07-1336-166/+361
|
* 1777 - consistent terminology: 'product'Kartik K. Agaram2015-07-134-9/+9
|
* 1776Kartik K. Agaram2015-07-131-0/+0
|
* 1775Kartik K. Agaram2015-07-133-2/+2
|
* 1774Kartik K. Agaram2015-07-133-4/+4
|
* 1773 - update all mu recipes to new-default-spaceKartik K. Agaram2015-07-1314-113/+113
| | | | | Turns out to not affect memory utilization or run-time. At all. But still looks nicer and requires less fudging on our part.
* 1772 - stop wasting space when allocating default-spaceKartik K. Agaram2015-07-131-0/+47
| | | | Let's see how much this helps edit.mu.
* 1771Kartik K. Agaram2015-07-132-1/+16
|
* 1770 - globals now work with namesKartik K. Agaram2015-07-131-2/+23
| | | | We won't bother supporting names for globals, for now.
* 1769 - routines can now have global variablesKartik K. Agaram2015-07-133-12/+54
|
* 1768Kartik K. Agaram2015-07-137-0/+0
|
* 1767Kartik K. Agaram2015-07-133-0/+0
|
* 1766Kartik K. Agaram2015-07-1245-2001/+1851
|
* 1765Kartik K. Agaram2015-07-111-18/+52
| | | | | As usual, trying to fix this manually was a false economy. Writing this test in the first place would have made debugging much simpler.
* 1764 - editor now updates all sandboxesKartik K. Agaram2015-07-113-15/+61
| | | | Finally, albeit too late for my demo.
* 1763 - warn on break/loop outside {}Kartik K. Agaram2015-07-111-85/+54
|
* 1762 - numbers without types = literalsKartik K. Agaram2015-07-111-0/+4
| | | | Quick hack for demo at balisp meetup today.
* 1761 - multiple sandboxes seems to be workingKartik K. Agaram2015-07-111-1/+0
| | | | No idea why this was wrong, but whatever..
* 1760 - failing test for multiple sandboxesKartik K. Agaram2015-07-111-53/+76
| | | | | | | | | We're starting to hit the limits of my 8GB RAM, to the point where I'm starting to economize on the size of the screen. Time to start thinking about reclaiming memory. Anyways, test now fails in the right place. I'm failing to propertly render intermediate lines between sandboxes.
* 1759Kartik K. Agaram2015-07-112-2/+6
|
* 1758 - now clear sandbox editor on F10Kartik K. Agaram2015-07-111-13/+47
| | | | We're ready to start displaying multiple sandboxes.
* 1757Kartik K. Agaram2015-07-111-7/+12
|
* 1756Kartik K. Agaram2015-07-111-7/+19
|
* 1755Kartik K. Agaram2015-07-101-13/+13
|
* 1754Kartik K. Agaram2015-07-103-16/+19
|
* 1753 - all tests passing againKartik K. Agaram2015-07-101-41/+47
| | | | Cleanup below editors is now all done.
* 1752 - cursor positioning fixedKartik K. Agaram2015-07-101-6/+8
|
* 1751 - sluggishness fixedKartik K. Agaram2015-07-103-38/+23
| | | | | | | Ah, I was indeed double-rendering, but somehow it was still hard to see the problem past that preliminary diagnosis. Still two failing tests to fix.
* 1750Kartik K. Agaram2015-07-101-0/+1
| | | | | No, that's a false alarm. There's just a larger screen to manipulate. But the size of the screen doesn't change in interactive mode.
* 1749 - investigating yesterday's sluggishnessKartik K. Agaram2015-07-101-2/+21
| | | | | | Comparing trace counts for a single test before and after yesterday's changes, one obvious culprit is that print-character has blown up from 754 trace lines (at all levels) to 2554.
* 1748Kartik K. Agaram2015-07-101-3/+3
|
* 1747Kartik K. Agaram2015-07-101-4/+3
|
* 1746 - load file and run a single testKartik K. Agaram2015-07-102-8/+7
| | | | $ ./mu test run-instruction-and-print-warnings
* 1745 - hoist warning/response strings out of editor-dataKartik K. Agaram2015-07-103-278/+326
| | | | | | | | | | Still ugly as hell. Some tests failing, but they're most likely wrong. We need to test cursor positioning at the level of the environment and take it away from the responsibilities of individual editors. Also bring back the line at the bottom of each editor. The non-test run ('main' in edit.mu) is completely borked. Sluggish as hell, and I can't seem to switch focus to the sandbox editor.
* 1744 - support just two editors rather than a listKartik K. Agaram2015-07-094-245/+171
| | | | | Current model: you click on something to put it on the editor at the top of the column. Worth a shot.