181–190 of 208 posts
I use this plain text planner / calendar every day and I love it, if I can say so myself, since I made it too. I've been using it for a few years now and I can say that it has definitely made me more productive. https://crushentropy.com/ You can plan and log your day in plain text and it visualizes your schedule. Markdown for planning, if you will.
That's a great name for a planning tool.
I recently just upped my StandardNotes subscription (the Black Friday ad is still active), and I'm now locked in for ~5.5 years. It's a very plain-text webapp/mobile app that aims to be simple and long-lasting, yet feature-full by means of optional extensions. It's not perfect, but I've been using it for a few months now without any data loss/major bugs encountered, and was excited to use it to ditch Google Keep/Goog…
Markdown is not plain text. Markdown destroys your single newlines. Plain text does not.
The output of Markdown processing is not.
Markdown is intended to be readable without processing as its syntax is mostly based on plain text email conventions. You should consider the ability to process Markdown to another output format to be an almost incidental benefit to using Markdown, rather than its primary function; meaning, Markdown syntax conveys semantics even without processing.
Its line behavior is based on plain text email client conventions, and plain text editor behavior, which many do not by default perform line wrapping, nor necessarily should, depending on user preference. Meaning, a Markdown file should be readable with line wrapping turned off, hence why it consumes line breaks, unless you use two spaces at the end of a line to override this behavior. (Think of the two spaces as an invisible rendering hint to Markdown processors.)
Email line length specifications: https://tools.ietf.org/html/rfc2822#section-2.1.1
I use this plain text planner / calendar every day and I love it, if I can say so myself, since I made it too. I've been using it for a few years now and I can say that it has definitely made me more productive. https://crushentropy.com/ You can plan and log your day in plain text and it visualizes your schedule. Markdown for planning, if you will.
This is awesome, have been looking for something like this for a while, wondering if there's a way to export it to and from my ical
I use this plain text planner / calendar every day and I love it, if I can say so myself, since I made it too. I've been using it for a few years now and I can say that it has definitely made me more productive. https://crushentropy.com/ You can plan and log your day in plain text and it visualizes your schedule. Markdown for planning, if you will.
Looks really good! Any chance for the code?
I use this plain text planner / calendar every day and I love it, if I can say so myself, since I made it too. I've been using it for a few years now and I can say that it has definitely made me more productive. https://crushentropy.com/ You can plan and log your day in plain text and it visualizes your schedule. Markdown for planning, if you will.
Sounds great. Did you open source the parser?
Earlier quoted context omitted.
This will open all of the files with TODO in them in vim: alias todogrep="vim $(grep TODO . -rl)" You can modify this easily, such as by using ripgrep, adding excludes, or doing regex to find TODO and FIXME together, but this is a quick one-liner to add to your `.bashrc`.
You can put the grep flags at the end? All these years, and I had no idea.
Earlier quoted context omitted.
Markdown is not plain text. Markdown destroys your single newlines. Plain text does not.
Markdown is plain text. The output of Markdown processing is not. Markdown is intended to be readable without processing as its syntax is mostly based on plain text email conventions. You should consider the ability to process Markdown to another output format to be an almost incidental benefit to using Markdown, rather than its primary function; meaning, Markdown syntax conveys semantics even without processing. Its…
> and plain text editor behavior, which many do not by default perform line wrapping
Not true, in a plain text editor you can make ascii art, or a dashed list of items, without having to type special syntax, and it will not become one long line
Dynamic line wrapping for display is something different than removing newline characters ("\n") you type in the string. Markdown does the latter. Text editors do not remove newlines you type.
> plain text email client conventions
I don't think plain text email ever removes a deliberate newline you type either. Does it?
And yet, the site uses a favicon of a typewriter ( https://plaintextproject.online/favicon.png ). It's so hard to be pure in this world!
It's something I don't like about what programmers tend to mean when they say plain text: Plain text isn't the same as ASCII. It isn't the same as Latin-1 or some other eight-bit encoding. UTF-8 is plain text. UTF-16 is plain text, too, but UTF-8 is better to use on the Internet. My point is that you can go well beyond the Latin alphabet and still be in the world of plain text. You can have correct quotes, as opposed…
That said, I think it's important to remember that plain text is still a binary format under the hood. Its power comes from its simplicity and many independent implementations. There's a lesson there for designing software in general, especially APIs and protocols.
I also think it's somewhat unfortunate that breaking changes were made to the plain text "API" along the way, in the form of Unicode. Unicode is great, but I wish it wasn't conflated so much with the original plain text. Plus it adds significant complexity. Sure, you can view a plain text file from 1991 in today's editors, but you can't view a Unicode file in an editor from 1991. And it's not apparent to the user why that is.
I love plain text, and generally agree with the principles here. That said, I think it's important to remember that plain text is still a binary format under the hood. Its power comes from its simplicity and many independent implementations. There's a lesson there for designing software in general, especially APIs and protocols. I also think it's somewhat unfortunate that breaking changes were made to the plain text…