Tools for removing "errors" from your writing

Initially, I was going to title this either “How to improve your writing”, or “How to write better”. But both those are subjective. The current title is apter1 , I think. In technical terms, these are errors/warnings in the prose. Errors you must fix. Warnings you should fix, but can choose to ignore. Since the “prose” isn't compiled, there is no compiler. This is similar to various interpreted (programming) languages, where there are no compilers, hence there is no easy way to catch the errors/warnings before hand.

GitLab: The project you were looking for could not be found

Every now and then I used to keep getting this error. (The project existed.) This error showed up once in a while. My go to solution was to reboot the machine (cause it used to work) But for once, that too did not work, and it led me to finding the real cause /solution. I'm glad I did. I had noticed that I get this error when SourceTree asks for passphrase for some other publickey.

Mindfulness Course : Week 1

I started an online course called “Mindfullness for Wellbeing and Peak Performance” at Monash University on FutureLearn. (Name of the course is a mouthful, hence I decided to shorten the name as referenced in this post) These are my notes from Week 1 Mindfulness means being engaged and present in the moment. We are usually mindful during the activities that we enjoy. When we are not happy is when our mind wanders off (to worry, thinking about the past or the future) and so that is when we need to be mindful.

Ulysses Pact

While listening to the Changelog Episode 221, where they interview Dr. Cory Doctorow. In the Interview, Doctorow mentioned Ulysses Pact. In the Greek mythology, it is said that whenever ship passes near the Siren's island, the men would hear Siren's Song. upon which they would lose their rational thought and jump the ship to swim towards the Siren's island. (Sirens would kill the men) Ulysses wanted to hear the Siren's Song, but he also knew the risks.

Prevent *scratch* buffer from getting killed

I started using persistent *scratch* buffer few months ago. You can read about it here It worked well for some time, and then at least couple of times, I noticed that when I restart emacs (does not happen very often) my *scratch* buffer is empty. So I started doing M-x persistent-scratch-save every time I was done writing to *scratch*, even though persistent-scratch-autosave-mode was ON Just recently I realized that I had “lost” my *scratch* buffer while still within my emacs session (It did not show up in the buffer list) So then I realized why I might be losing the contents.