about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 2207Kartik K. Agaram2015-09-261-1/+1
|
* 2206 - fix missing ingredientsKartik K. Agaram2015-09-263-5/+5
| | | | | How the heck was this working until now? There must be redundant moves. And was I clobbering test data?
* 2205 - warn on missing ingredientKartik K. Agaram2015-09-182-1/+13
| | | | ..unless you explicitly ignore the found? result.
* 2204Kartik K. Agaram2015-09-161-2/+8
|
* 2203 - show recipe warnings in 'mu sandbox'Kartik K. Agaram2015-09-152-9/+8
|
* 2202 - don't let editor die on syntax errorsKartik K. Agaram2015-09-153-35/+50
| | | | | Bugfix to 2186. I hadn't taken care of 'reload' as cleanly as I had 'run-interactive'.
* 2201Kartik K. Agaram2015-09-151-2/+4
|
* 2200Kartik K. Agaram2015-09-152-10/+14
|
* 2199 - stop printing numbers in scientific notationKartik K. Agaram2015-09-1413-33/+79
| | | | | | | | | | | Turns out the default format for printing floating point numbers is neither 'scientific' nor 'fixed' even though those are the only two options offered. Reading the C++ standard I found out that the default (modulo locale changes) is basically the same as the printf "%g" format. And "%g" is basically the shorter of: a) %f with trailing zeros trimmed b) %e So we'll just do %f and trim trailing zeros.
* 2197Kartik K. Agaram2015-09-141-1/+1
|
* 2196Kartik K. Agaram2015-09-142-3/+1
|
* 2195Kartik K. Agaram2015-09-141-2/+2
|
* 2194Kartik K. Agaram2015-09-141-2/+2
|
* 2193Kartik K. Agaram2015-09-141-2/+2
|
* 2192Kartik K. Agaram2015-09-141-0/+1
|
* 2191Kartik K. Agaram2015-09-131-28/+26
|
* 2190Kartik K. Agaram2015-09-121-2/+3
|
* 2189Kartik K. Agaram2015-09-121-1/+1
|
* 2188Kartik K. Agaram2015-09-121-2/+2
|
* 2187Kartik K. Agaram2015-09-122-1/+5
|
* 2186 - kill the current routine on first errorKartik K. Agaram2015-09-122-4/+35
| | | | | Exception: allow run-interactive to continue even if it encounters errors in parsing its ingredient as mu code.
* 2185Kartik K. Agaram2015-09-121-0/+1
|
* 2184 - bugfix in trace_countKartik K. Agaram2015-09-122-3/+12
| | | | | | | | | | | | | | | | It was reading lines like this in scenarios: -warn: f: error error as: -warn: f which was causing them to be silently ignored. Also found an insane preprocessor expansion from not parenthesizing preprocessor arguments. SIZE(end+delim) worked even when end was an integer, but it happily didn't ever get the wrong answer.
* 2183 - environment + external editor using tmuxKartik K. Agaram2015-09-1220-19/+8346
| | | | Thanks Jack and Caleb Couch for the idea.
* 2182Kartik K. Agaram2015-09-122-3/+1
|
* 2181 - detect shift-tabKartik K. Agaram2015-09-112-5/+10
| | | | Does nothing useful yet, though.
* 2180 - render the trace even if there's warningsKartik K. Agaram2015-09-102-1/+53
|
* 2179 - undo bugfixKartik K. Agaram2015-09-102-1/+22
|
* 2178 - don't die on divide by 0Kartik K. Agaram2015-09-101-6/+25
|
* 2177Kartik K. Agaram2015-09-0738-9349/+12357
|
* 2176Kartik K. Agaram2015-09-062-3/+35
|
* 2175Kartik K. Agaram2015-09-0655-2999/+3437
|
* 2174Kartik K. Agaram2015-09-061-1/+2
|
* 2173 - 'main' for 'mu edit' running layers 1 and 2Kartik K. Agaram2015-09-061-1/+42
| | | | | | Layer 2 provides an almost fully functioning interactive editor: $ ./mu edit/00[12]* -- abcdef
* 2172 - 'main' for 'mu edit' running just layer 1Kartik K. Agaram2015-09-062-1/+14
| | | | | | | | | Takes the text to render inside the editor on the commandline: $ ./mu edit/001-editor.mu -- abcdef Layer 1 has no interactivity. Just shows the text you pass in on the commandline, wrapping as you would expect. Press any key to exit.
* 2171 - 'main' can take ingredients from the shellKartik K. Agaram2015-09-062-6/+39
| | | | | | | | | | Ingredients of 'main' are always strings (type address:array:character), and are delineated from .mu files to load by a "--", e.g.: $ ./mu x.mu y.mu -- a b c Here 'main' must be defined in one of x.mu and y.mu, and will receive the ingredients "a", "b", and "c".
* 2170Kartik K. Agaram2015-09-061-15/+22
|
* 2169Kartik K. Agaram2015-09-061-1/+0
|
* 2168Kartik K. Agaram2015-09-061-1/+0
|
* 2167Kartik K. Agaram2015-09-052-4/+18
|
* 2166Kartik K. Agaram2015-09-053-168/+221
|
* 2165Kartik K. Agaram2015-09-051-1/+1
|
* 2164Kartik K. Agaram2015-09-051-2/+1
|
* 2163Kartik K. Agaram2015-09-053-17/+19
| | | | | | | | `render-string` (and `render-code-string`; ugh) should start a new line after, not before, like everybody else. I've been meaning to fix this for a long time, but now I have to, to move the warnings fields out of early layers.
* 2162Kartik K. Agaram2015-09-051-16/+2
|
* 2161Kartik K. Agaram2015-09-051-8/+8
| | | | | Starting on making the basic programming environment oblivious to warnings. That should come later.
* 2160Kartik K. Agaram2015-09-054-0/+0
|
* 2159Kartik K. Agaram2015-09-052-139/+139
|
* 2158Kartik K. Agaram2015-09-051-1/+7
|
* 2157 - edit/ now contains real layersKartik K. Agaram2015-09-054-48/+74
| | | | | | | | | To run just until say layer 6, say this: $ ./mu test edit/00[0-6]* The layers are not perfect yet; there might be a few things (like the warning fields) that need to move to a later layer.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-07-01 00:16:42 +0000