A plain text note-taking system for problem solving
calculist.io
calculist.io
The web version is not for collaboration, it’s for subscription income.
I would absolutely purchase this if it were packaged as an Android app.
Also, the desktop app (which will be available within the next few days) is 100% local, no internet connection necessary, and 100% private.
It's nice to let separate programs do the encryption/storage vs the editing.
* \= 2*3
* \(x, y) = x+y
However I'm not sure how to define a new function. Here's what I tried: * \: foo (x, y) = x+y # no error
* \=foo(2, 3) # error
* \:barr = 2*3 # no error
* \=barr # error\= foo(2, 3)
There's slightly outdated documentation on github: https://github.com/calculist/calculist/wiki/Keyboard-Shortcu...
I'm working on getting things updated now. More documentation will be available over the next few weeks.
I tried the demo and expanded the items in the sample document. I saw examples of calculation! So I’d love to see examples of problem solving with Calculist.
> Markdown is a lightweight markup language for creating formatted text
> Markdown, the simple and easy-to-use markup language
> Markdown's syntax is intended for one purpose: to be used as a format for writing for the web
It's formatted text or also called rich text.
I'm currently brainstorming a notes platform for second order thinking[1], Say like a community submitted scenarios for second-order, third-order thinking. Would Calculist be a good fit for such notes?
[1] https://needgap.com/problems/263-plan-second-order-third-ord... (Disclaimer: My platform)
However, that clearly doesn’t apply to markup that is common enough to become a medium of communication.
Then, the question is, where to draw the line? One could argue that markdown only provides minimal semantic structure, and as such is akin to punctuation, which hasn’t always existed in ”plain text”, either.
I think some new categories are needed. Effectively, the standard ones would be something like:
1. Unstructured text: edited and viewed in plain text editor, formatting limited to whitespace
2. Rich text: edited and viewed in GUI editor with unconstrained structured and unstructured formatting
3. Structured text: markdown, LaTeX, etc. Edited as plain text with minimal markup, viewed by rendering source document in GUI, with automatic formatting based on structure and chosen style
4a. Program code, human-written and -readable
4b. Program code, automatically generated (JS bundles, etc)
5. Machine code as binary
1. Plain text: text without mark-up
2. Code and formatted/rich text (e.g. LaTeX, CSV, Markdown, HN comment): text with mark-up or conforming to a grammar with attached semantics.
3. binary (e.g. an ELF executable)
We wrote programs, which controlled a Roland DG DXY-880. That also used a plain text programing language.
I was not speaking a lot of English at that time, so mirror translating back from Hungarian, we said, "textual format" or "plain, textual format" ("síma, szöveges formátum"), to contrast its simplicity with binary formats.
(I was born and raised in Szeged though, so that could be just our regional dialect. How about you?)
- It is fully local web app .. no servers no data hoarding.
- No proprietary format, it saves your notes in markdown in your computer.
- It is WYSIWYG editor so that you don't have to switch context.
Funny, avoiding context switches is why I keep everything in plaintext...