wordgrinder VS epy

There are some people trying to recreate the Wordstar experience, like this one, and they supposedly were great and simple for writing long-form content (it was before my time, so I have no experience with it).

WordGrinder. It's great for distraction-free writing, and can output Markdown or troff. It's a great tool for getting words down, but its otherwise pretty limited (which I think is one of its strengths). When I need to print or generate a PDF, I have a little script.

For word processing there's WordGrinder, which is in the repos for many distros (in Fedora: dnf install wordgrinder). Things like LaTeX and Groff are for typesetting, which I don't view as the same as word processing. WordGrinder is more like the classical DOS word processors (e.g. WordPerfect 5.1).

Some other choices: * https://cowlark.com/wordgrinder * https://github.com/spartrekus/g-editor (WS compatible)

I have a word processor I wrote (https://cowlark.com/wordgrinder) which is mostly written in Lua, with hardware-specific stuff in C, and while this works extremely well, I'd very much like something with stronger typing. There's a possibility I'd be able to just drop in Luau and get it, plus some performance benefits. I'd need to reimplement parts of the standard library due to Luau having dropped things like the io library but that's no great hardship. I like the syntax, too, which is expressive and very lightweight.

There is Wordgrinder.

Try Epy CLI Ebook Reader

Hey there here is baca, epy's lovely sister. Built using the awesome textual project.

However, if you don't need all the bells and whistles of Foliate and Koreader, and you are willing to carry out some trials and errors, consider exploring other simpler options like epr/epy, in Linux you can use any terminal of your choice, whereas in Android probably you'll be better off using Termux (a simple pip install epr-reader should do).

Sure, i use epy[1] and every month i d/l my books from amazon that i have bought, dedrm[2] through calibre and save the epubs to a folder. Its not a particularly arduous task.

When i want to read i have an alias setup along the lines of:

epy "$(fzf)"

its a nice interface ;-)

Now i don't often read full books in the terminal, BUT i do like being able to reference bits that i remember at a VERY quick speed. I recently was talking to somoene about biases we bring to statistics and could remember reading a great anecdote about it, using rga[3] i was able to bring up the passage VERY quickly in the terminal

Like most great cli tools, its about the workflow

[1] https://github.com/wustho/epy

I used to dislike ebooks until I started using epy. Reading on the command line made it more enjoyable to read some technical books, especially since it can vertically split alongside vim or a console.

In the book section, I would recommend adding epy by the same author as epr. It’s an updated version with more features

From desktop open source TTS systems, I found mimic closest to being useful, and my preferred EPub reader (epy) can use it.

Here is cli one, worth a try: https://github.com/wustho/epy

I would substitute dateutils for 17 and wordgrinder for 3 instead of pdd and abiword. Also, p7zip instead of 20, zip and unzip. For calendar (18), I like gcal which could also be used as 29, reminder. For a nice TUI ebook reader, I like epy.

epy or Foliate on desktop. Really there are so many ways to read EPubs!