| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 2865 | Kartik K. Agaram | 2016-04-24 | 1 | -1/+1 |
| | | |||||
| * | 2833 | Kartik K. Agaram | 2016-04-14 | 1 | -1/+4 |
| | | |||||
| * | 2785 | Kartik K. Agaram | 2016-03-15 | 1 | -7/+12 |
| | | |||||
| * | 2783 - typo in Readme; thanks John Lamping | Kartik K. Agaram | 2016-03-14 | 1 | -2/+2 |
| | | |||||
| * | 2761 | Kartik K. Agaram | 2016-03-11 | 1 | -10/+8 |
| | | |||||
| * | 2758 | Kartik K. Agaram | 2016-03-10 | 1 | -4/+4 |
| | | |||||
| * | 2757 | Kartik K. Agaram | 2016-03-10 | 1 | -3/+3 |
| | | |||||
| * | 2756 | Kartik K. Agaram | 2016-03-10 | 1 | -6/+6 |
| | | |||||
| * | 2755 | Kartik K. Agaram | 2016-03-10 | 1 | -10/+1 |
| | | |||||
| * | 2754 | Kartik K. Agaram | 2016-03-10 | 1 | -2/+2 |
| | | |||||
| * | 2753 | Kartik K. Agaram | 2016-03-10 | 1 | -3/+3 |
| | | |||||
| * | 2752 | Kartik K. Agaram | 2016-03-10 | 1 | -1/+2 |
| | | |||||
| * | 2751 | Kartik K. Agaram | 2016-03-10 | 1 | -103/+31 |
| | | |||||
| * | 2750 - take out all philosophy from the Readme | Kartik K. Agaram | 2016-03-10 | 1 | -197/+61 |
| | | |||||
| * | 2747 | Kartik K. Agaram | 2016-03-09 | 1 | -0/+4 |
| | | | | | Thanks Ben Trask for engaging with my arguments. | ||||
| * | 2742 | Kartik K. Agaram | 2016-03-08 | 1 | -41/+2 |
| | | |||||
| * | 2738 | Kartik K. Agaram | 2016-03-08 | 1 | -16/+16 |
| | | |||||
| * | 2737 | Kartik K. Agaram | 2016-03-08 | 1 | -1/+1 |
| | | |||||
| * | 2735 - define recipes using 'def' | Kartik K. Agaram | 2016-03-08 | 1 | -29/+29 |
| | | | | | | | | | | | | | I'm dropping all mention of 'recipe' terminology from the Readme. That way I hope to avoid further bike-shedding discussions while I very slowly decide on the right terminology with my students. I could be smarter in my error messages and use 'recipe' when code uses it and 'function' otherwise. But what about other words like ingredient? It would all add complexity that I'm not yet sure is worthwhile. But I do want separate experiences for veteran programmers reading about Mu on github and for people learning programming using Mu. | ||||
| * | 2734 | Kartik K. Agaram | 2016-03-08 | 1 | -7/+7 |
| | | |||||
| * | 2733 | Kartik K. Agaram | 2016-03-07 | 1 | -0/+2 |
| | | |||||
| * | 2732 | Kartik K. Agaram | 2016-03-07 | 1 | -1/+10 |
| | | |||||
| * | 2731 | Kartik K. Agaram | 2016-03-07 | 1 | -1/+1 |
| | | |||||
| * | 2730 | Kartik K. Agaram | 2016-03-07 | 1 | -43/+159 |
| | | |||||
| * | 2729 | Kartik K. Agaram | 2016-03-06 | 1 | -7/+12 |
| | | |||||
| * | 2723 | Kartik K. Agaram | 2016-02-29 | 1 | -5/+2 |
| | | |||||
| * | 2651 | Kartik K. Agaram | 2016-02-12 | 1 | -7/+2 |
| | | |||||
| * | 2650 | Kartik K. Agaram | 2016-02-12 | 1 | -4/+4 |
| | | |||||
| * | 2562 | Kartik K. Agaram | 2016-01-17 | 1 | -1/+1 |
| | | | | | | | | | | | | | We want to use the type 'recipe' for recipe *variables*, because it seems nicer to say `recipe number -> number` rather than recipe-ordinal, etc. To support this we'll allow recipe names to be mentioned without any type. This might make a couple of places in this commit more brittle. I'm dropping error messages, causing them to not happen in some situations. Maybe I should just bite the bullet and require an explicit :recipe-literal. We'll see. | ||||
| * | 2437 | Kartik K. Agaram | 2015-11-14 | 1 | -3/+4 |
| | | |||||
| * | 2427 | Kartik K. Agaram | 2015-11-12 | 1 | -3/+3 |
| | | |||||
| * | 2426 | Kartik K. Agaram | 2015-11-11 | 1 | -5/+62 |
| | | |||||
| * | 2425 | Kartik K. Agaram | 2015-11-10 | 1 | -7/+8 |
| | | |||||
| * | 2176 | Kartik K. Agaram | 2015-09-06 | 1 | -3/+3 |
| | | |||||
| * | 2156 - split edit.mu into multiple files | Kartik K. Agaram | 2015-09-05 | 1 | -2/+2 |
| | | | | | | | | | | Now you can bring up the programming environment by saying: $ mu edit The files under edit aren't yet *layers*, though, they have a few dependencies that we need to clean up. | ||||
| * | 2130 | Kartik K. Agaram | 2015-09-02 | 1 | -10/+7 |
| | | |||||
| * | 1985 | Kartik K. Agaram | 2015-08-13 | 1 | -2/+8 |
| | | |||||
| * | 1984 | Kartik K. Agaram | 2015-08-13 | 1 | -1/+1 |
| | | |||||
| * | 1983 | Kartik K. Agaram | 2015-08-13 | 1 | -16/+26 |
| | | |||||
| * | 1972 - resize Readme images to match text size | Kartik K. Agaram | 2015-08-10 | 1 | -3/+3 |
| | | | | | | | | | | | | | | Now that we have larger-res images for the Readme they look good even if the browser is magnified with ctrl-+ (like mine is). factorial-test.png looks about the same size as surrounding text at 250px wide. Original size is 330px. factorial.png original size is 450px. So its width should be 340px. chessboard-test.png original size is 423px. So its width should be 320px. | ||||
| * | 1971 | Kartik K. Agaram | 2015-08-10 | 1 | -49/+62 |
| | | |||||
| * | 1894 | Kartik K. Agaram | 2015-07-30 | 1 | -0/+18 |
| | | |||||
| * | 1893 | Kartik K. Agaram | 2015-07-29 | 1 | -6/+6 |
| | | |||||
| * | 1885 | Kartik K. Agaram | 2015-07-29 | 1 | -2/+3 |
| | | |||||
| * | 1868 - start using naked literals everywhere | Kartik K. Agaram | 2015-07-28 | 1 | -6/+6 |
| | | | | | First step to reducing typing burden. Next step: inferring types. | ||||
| * | 1777 - consistent terminology: 'product' | Kartik K. Agaram | 2015-07-13 | 1 | -5/+5 |
| | | |||||
| * | 1775 | Kartik K. Agaram | 2015-07-13 | 1 | -2/+2 |
| | | |||||
| * | 1774 | Kartik K. Agaram | 2015-07-13 | 1 | -3/+3 |
| | | |||||
| * | 1713 | Kartik K. Agaram | 2015-07-05 | 1 | -8/+8 |
| | | | | | Less objectionable placeholder for syntax highlighting mu fragments. | ||||
| * | 1712 | Kartik K. Agaram | 2015-07-05 | 1 | -1/+5 |
| | | |||||