[gala8y]

> I like to keep a scratch file

Thanks. I think I am doing something very similiar and will definitely stay close to bare text (Markdown). Your comment shows me that there is no escape from marking up text (places where sth was deleted or some auxiliary header) and working through text couple of times, probably making some copies along way.

> I'll also use diff tools built into Vim/Neovim

Diffing workflow is completely out of bauds for me, maybe will try to learn some new ways in close future (Vim/Spacemacs in general). If you could say some more on how you quickly see diffs, that would be great. Are you using version control for this?

As a side note, I see that it just takes time to tune mind to work efficiently with bigger pieces these days. Modern times, refocus req'ed.

Your comment was very helpful for me, thank you.

[rogeruiz]

If you're more familiar with VSCode, you could use it as your visual diff tool, https://vscode.one/diff-vscode/

But essentially I only ever care about two versions of my writing. The current version that has been edited, and the previous version that basis for the editing. This lets me not have to put things in version control and allows me to only ever really have two versions of something on my plate at any given moment.

If you are more comfortable in the Terminal, you could use a tool like `opendiff` as well which just shows you the lines that have changed. I normally only do this after I have had some rest in between the document revisions. But this view will produce a diff and also is good when you're unsure about certain sections.

I'll part on one last piece of advice which is that you should focus on the goal of what you're doing and pick up new things along the way. What works for me might not work for you exactly and you might have better ways of approach the same given problem. Don't sweat the details until you have enough of them in your tool belt. Good luck!