Skip to Content

2019-09-01 00:00:00 -0400 EDT

I’ve not used a computer much this past month, and I stopped using them at a bad time: shortly after transitioning to using a raspberry pi as my sole computer, and using Emacs as my main “operating system.”

I had just started to write my own personal web server in Elisp, and was beginning to consider writing my own markup syntax based on it, too. Depending, this journal itself might be in that format. But, at the moment, I don’t have any sort of parser for it. I figure it might be better to write up some sample text first, since I know what I’d like it to look like, and then figure out how to make the parser match that. Like, if I don’t even know what I can parse, I won’t have preconceptions and so will just make up the best little markup language for me.

My biggest project is still my web server - or well, the highest priority. It’s a pretty abstract thing, designed as a responsive object server that converts various bits of my personal or project information into a standard format, and then renders that and serves it up. The reason it’s the highest priority is because each of the other projects will then have their own functions for converting their data into that type of object, and taking it and rendering it.

Though, I’m not entirely sure where it is I’ll be writing those functions. For example, I have a file “ems-library.el”, and it has its own data structure. Should the functions for turning that data into a rosian object and rendering it as various things be in that file, or in the “ems-ros” file?

I’m inclined toward the latter, so that (code ems-ros.el) will have its core functions, and then an increasingly large collection of functions for converting other data structures to rosian objects, and rendering a variety of different object types.

Not that it really matters, since all this is for personal use, for now, and it’s easy enough to refactor things.