51–60 of 95 posts
ctrl+d to exit.
You can edit the current line (to fix spelling misteaks) but not anything else. You can reference as much as your terminal shows.
This is a perfect example of the superiority of the Unix way. Simple programs that do one thing and work well together, combined into things their authors didn't think of. This is my idea of beauty.
Shameless plug - my app, Writing Streak, has the "typewriter" mode (Alt+T) that prevents you from editing the text you wrote, and a "blurred" mode (Alt+B) that hides the text you type, achieving the same effect: https://writingstreak.io
Does it support overstriking? Typing o/ is a legitimately good way to type ø, for example; it isn't a universal input method by any stretch but when it works, it's very mnemonic.
This might be an unpopular opinion but I always edit while writing my first draft. This is how I've written 250+ technical blog posts and over a million words worth of course notes. I basically write a couple of sentences or paragraphs, stop, review, reword things if needed, change things around and move on. Then at the very end I'll give it all a final reordering / fixing until I'm happy with it. I feel like I can't…
The "never edit while drafting" advice comes from the creative writing community. It might be of limited use in cases like technical writing, where you already might have a solid idea what the final product should look like before you start. Most people find that trying to write a novel and edit it at the same time is like baking cookies one by one.
This might be an unpopular opinion but I always edit while writing my first draft. This is how I've written 250+ technical blog posts and over a million words worth of course notes. I basically write a couple of sentences or paragraphs, stop, review, reword things if needed, change things around and move on. Then at the very end I'll give it all a final reordering / fixing until I'm happy with it. I feel like I can't…
For this reason I trained myself to make the first draft the final draft. Now with computers this is no longer relevant as I'm not hand writing multiple drafts on paper.
There are other factors, but I think this one is major for a lot of people.
This might be an unpopular opinion but I always edit while writing my first draft. This is how I've written 250+ technical blog posts and over a million words worth of course notes. I basically write a couple of sentences or paragraphs, stop, review, reword things if needed, change things around and move on. Then at the very end I'll give it all a final reordering / fixing until I'm happy with it. I feel like I can't…
Among professional authors, John Scalzi has said many times that he edits as he goes along[1]. For shorter academic and work pieces (and back when I blogged) I’ve done this as well, but I do an outline for longer papers first, and then edit as I go. Of course I wasn’t anywhere near nickjj’s level of output. [1] https://www.panmacmillan.com/blogs/science-fiction-and-fanta...
cat /dev/stdin > yourfile.txt ctrl+d to exit. You can edit the current line (to fix spelling misteaks) but not anything else. You can reference as much as your terminal shows. This is a perfect example of the superiority of the Unix way. Simple programs that do one thing and work well together, combined into things their authors didn't think of. This is my idea of beauty.
cat > yourfile.txt
This strategy seems like it makes it very difficult to write. What if you lose track of what you've already said? It seems like a better solution is to just disable backspace.
But I'm not sure what the point is. I mean, searching yields "We couldn’t find any repositories matching 'rolandasb'". And I'm certainly not going to write anything substantive on this site. So how would I do this locally?