> I’ve brought my text files with me since 1990, from Mac to Windows to Linux to BSD > But plain text? Always. Everywhere. Quite obviously you have your files in ASCII. Anyone who needs more than 26 letters (or god forbid non-latin ones) are fucked. Sometimes quite literally. > Your writing should outlive you. Depending on companies is not an option. ASCII? Sure. EBCDIC? Ughh. UTF... 8? 16? 32? > If you rely on Word,…
Write plain text files
101–110 of 425 posts
Re: Write plain text files
#102PS. I am not the author or contributor just a daily user of it and i like it.
Re: Write plain text files
#103Re: Write plain text files
#104I use plain text because there is no multimedia equivalent that is universal and end-user controlled, and there are no multimedia equivalents to Vim, Grep, regex, etc. Text is great, but an image, table, or diagram are sometimes irreplaceable. We think we are great innovators, but we are stuck in 1990. Notice also that there are no Vim-equivalents for phones, even though that platform has been widely used for 15+ yea…
Re: Write plain text files
#105I tend to go for (simple) markdown rather than pure text files. It can be rendered into some fancy format, but the source code is also readable to humans. With chat apps like Slack and Discord taking it up, even non-technical people tend to understand what it means to put emphasis on something. You get the benefits of plain text with the ability to empathise, without fancy formats. Such a format also enforces paragra…
This is my experience as well. I admire anyone that goes full .txt but I missed how easily markdown allows me to hierarchically organize my thoughts via headings and sub-headings.
Re: Write plain text files
#106I've tried a lot of different things over decades. And, after countless experimentation, I'm still at the same place... I store data all over the place. I have Evernote for long book notes and tracking financial data. I'm using notion right now as my base of notes for learning how to build a cabin (toggles and embedding videos is wonderful). I tried to really use roam and its off-shots for a while but could never rea…
> and 90% of the time, I never look at them again So, you’re a note squirrel. So am I. I’ve stopped caring or stressing out about it. I just accept that I’m never going to be overly organized or systematic. I do keep all of my notes in a /notes folder or sub folder so that fuzzy find works nicely. That’s the extent of my organization.
Re: Write plain text files
#107I keep all my txt file notes in GitHub repos, works great for me. One thing I’m still trying to solve, taking new notes while I’m mobile. I haven’t found a good easy way to create/edit notes and commit them to git while I’m on my iPhone. The GitHub mobile app does not allow editing. The GitHub website does but it’s clumsy to use on a mobile device. Anyone have suggestions for a solution?
Re: Write plain text files
#108I've been using iA Writer for all of my text and writing needs for many years, couldn't be happier. https://ia.net/writer
Re: Write plain text files
#109I use plain text because there is no multimedia equivalent that is universal and end-user controlled, and there are no multimedia equivalents to Vim, Grep, regex, etc. Text is great, but an image, table, or diagram are sometimes irreplaceable. We think we are great innovators, but we are stuck in 1990. Notice also that there are no Vim-equivalents for phones, even though that platform has been widely used for 15+ yea…
Vim for phones sounds like trying to play doom on my fridge. Possible, not enjoyable.
Re: Write plain text files
#110> I’ve brought my text files with me since 1990, from Mac to Windows to Linux to BSD > But plain text? Always. Everywhere. Quite obviously you have your files in ASCII. Anyone who needs more than 26 letters (or god forbid non-latin ones) are fucked. Sometimes quite literally. > Your writing should outlive you. Depending on companies is not an option. ASCII? Sure. EBCDIC? Ughh. UTF... 8? 16? 32? > If you rely on Word,…