about summary refs log tree commit diff stats
path: root/apps
Commit message (Collapse)AuthorAgeFilesLines
* .Kartik K. Agaram2021-10-171-1/+0
|
* primitive: read line from keyboardKartik K. Agaram2021-10-131-19/+1
| | | | Blocking.
* support arrow keys in apps/ex7.muKartik K. Agaram2021-09-041-4/+4
|
* fix apps/ex7.muKartik K. Agaram2021-09-041-2/+1
| | | | I'm increasingly missing CI.
* a tamil example (that I can't read)Kartik K. Agaram2021-09-031-5/+19
|
* support combining characters in streams of textKartik K. Agaram2021-09-021-0/+55
| | | | Fake screens can't handle them yet.
* .Kartik K. Agaram2021-09-021-11/+12
|
* .Kartik K. Agaram2021-09-021-3/+3
| | | | A more common hindi vowel.
* a few more examples of combining charactersKartik K. Agaram2021-09-011-2/+45
|
* rendering code-points with combining charactersKartik K. Agaram2021-09-012-7/+38
| | | | | | | There's a new example app showing this ability. Still to go: support for combining characters when rendering text and streams.
* .Kartik K. Agaram2021-08-301-1/+1
| | | | Open question fixed.
* first rendering of non-latin scriptKartik K. Agaram2021-08-301-0/+27
| | | | | Open question: why does column 0 get cropped? The spacing also seems excessive. Are we taking up 3 grid points?
* fix bad terminology: grapheme -> code pointKartik K. Agaram2021-08-292-6/+6
| | | | | | | | | | Unix text-mode terminals transparently support utf-8 these days, and so I treat utf-8 sequences (which I call graphemes in Mu) as fundamental. I then blindly carried over this state of affairs to bare-metal Mu, where it makes no sense. If you don't have a terminal handling font-rendering for you, fonts are most often indexed by code points and not utf-8 sequences.
* .Kartik K. Agaram2021-08-2913-26/+3
|
* render wide glyphs in the fontKartik K. Agaram2021-08-291-0/+2
|
* width-aware drawing primitivesKartik K. Agaram2021-08-291-1/+1
| | | | No support yet for drawing wide graphemes.
* .Kartik K. Agaram2021-08-282-5/+3
|
* .Kartik K. Agaram2021-07-291-1/+1
|
* .Kartik K. Agaram2021-07-281-11/+0
|
* .Kartik K. Agaram2021-07-261-0/+74
|
* .Kartik K. Agaram2021-07-261-0/+2
|
* .Kartik K. Agaram2021-07-262-4/+16
|
* game of life in lispKartik K. Agaram2021-07-261-18/+18
| | | | | | | | Super slow; each frame is cleared as a sort of progress indicator while it computes the next frame. In the process I realize I need to adjust every single trace in the shell sources to be more fault-tolerant to a filled-up trace stream.
* .Kartik K. Agaram2021-07-191-176/+0
|
* .Kartik K. Agaram2021-07-162-1133/+23
|
* more powerful load-sectorsKartik K. Agaram2021-07-162-18/+3
|
* .Kartik K. Agaram2021-07-162-18/+18
|
* .Kartik K. Agaram2021-07-1622-0/+4508
|
* 7842 - new directory organizationKartik K. Agaram2021-03-03125-387821/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Baremetal is now the default build target and therefore has its sources at the top-level. Baremetal programs build using the phase-2 Mu toolchain that requires a Linux kernel. This phase-2 codebase which used to be at the top-level is now under the linux/ directory. Finally, the phase-2 toolchain, while self-hosting, has a way to bootstrap from a C implementation, which is now stored in linux/bootstrap. The bootstrap C implementation uses some literate programming tools that are now in linux/bootstrap/tools. So the whole thing has gotten inverted. Each directory should build one artifact and include the main sources (along with standard library). Tools used for building it are relegated to sub-directories, even though those tools are often useful in their own right, and have had lots of interesting programs written using them. A couple of things have gotten dropped in this process: - I had old ways to run on just a Linux kernel, or with a Soso kernel. No more. - I had some old tooling for running a single test at the cursor. I haven't used that lately. Maybe I'll bring it back one day. The reorg isn't done yet. Still to do: - redo documentation everywhere. All the README files, all other markdown, particularly vocabulary.md. - clean up how-to-run comments at the start of programs everywhere - rethink what to do with the html/ directory. Do we even want to keep supporting it? In spite of these shortcomings, all the scripts at the top-level, linux/ and linux/bootstrap are working. The names of the scripts also feel reasonable. This is a good milestone to take stock at.
* 7841Kartik Agaram2021-03-0315-0/+0
|
* 7757Kartik K. Agaram2021-02-191-15/+0
|
* 7730 - baremetal/shell: boolean valuesKartik K. Agaram2021-02-122-3/+3
| | | | | In the process I found a bug in the Mu compiler. Limitations of just asserting the emitted code but not running it.
* 7700Kartik Agaram2021-02-091-0/+73
|
* 7692Kartik Agaram2021-02-073-6/+33
| | | | | It's bad enough that metadata comments are restricted to integer literals; let's at least make them work on _all_ integer literals.
* 7690Kartik Agaram2021-02-0732-436/+436
| | | | Convert comments about magic constants into metadata.
* 7689 - permit metadata on Mu literal integersKartik Agaram2021-02-062-0/+33
| | | | | | | | | | | | | | Metadata is always ignored. It's purely for documentation purposes. But as long as Mu has no named constants it's starting to feel increasingly essential. I'm still not going to bother to add metadata to other parts of the language. Let's see if we need them. Even though it's a little warty that the rules vary throughout the stack: - bare SubX: metadata everywhere - SubX with syntax sugar: no metadata in calls or addressing-mode sigil-expressions - Mu: metadata only for literal integers
* 7559 - reorganize sectors built in raw hexKartik Agaram2021-01-242-17/+17
| | | | | | | | | | | | | | | | | This was tedious for three reasons beyond the usual one of having to track and update offsets several time while I debug: - The Bochs troubles of the previous commit kept polluting my brain even though they were irrelevant. - I had to keep some changes locally to allow myself to use Bochs, which polluted my working directory. - I had to travel the long way to the realization that I'm not actually initializing the stack anywhere. BIOS was starting my stack off at 0x10000, which was promptly clobbered by my second read from disk. The good news: while I'm here I grow the interrupt descriptor table. So I don't have to go through this exercise when I get back to supporting the mouse.
* 7526Kartik Agaram2021-01-1615-0/+0
|
* 7490 - baremetal: draw a grapheme to screenKartik Agaram2021-01-091-0/+2
|
* 7489 - include GNU UnifontKartik Agaram2021-01-092-17/+17
| | | | | | | https://en.wikipedia.org/wiki/GNU_Unifont#The_.hex_font_format http://unifoundry.com/unifont/index.html Since GNU Unifont is covered under the GPL v2, so I believe is this repo.
* 7462 - SubX version of baremetal/ex2.subxKartik Agaram2020-12-292-1/+1
|
* 7460 - baremetal backend for SubXKartik Agaram2020-12-292-2178/+214
|
* 7459Kartik Agaram2020-12-292-102/+199
| | | | Bring baremetal variant up to date with recent changes.
* 7458Kartik Agaram2020-12-292-90/+184
| | | | Switch survey_elf to the new approach.
* 7457Kartik Agaram2020-12-282-10/+14
|
* 7456Kartik Agaram2020-12-281-2/+1
|
* 7454Kartik Agaram2020-12-284-338/+119
| | | | Go back to commit 7448.
* 7453Kartik Agaram2020-12-281-74/+23
| | | | | Snapshot: this approach of disambiguating /disp32 based on metadata doesn't work. The `survey` phase runs after `pack`, which gets rid of most metadata.
* 7452Kartik Agaram2020-12-284-24/+286
|
* 7451Kartik Agaram2020-12-284-20/+28
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-01 11:53:11 +0000