PLAIN TEXT WORKFLOW HOW TO
PLAIN TEXT WORKFLOW ARCHIVE

Copy the result to the clipboard or send it to Drafts ( app). Once complete you are immediately offered a menu with two options. The choice then runs one of three different regular expressions that carry out the specified trimming request. Next the workflow prompts you to select whether to trim before, after or at both ends of the lines of text. The third line has whitespace only after the visible text and the final line is a control having no whitespace. The second line has whitespace only before the visible text. The first line has whitespace before and after the visible text. The workflow starts by defining some sample text. The workflow can trim leading whitespace, trailing whitespace or both together.

PLAIN TEXT WORKFLOW HOW TO

This workflow shows how to trim whitespace from lines of text.

PLAIN TEXT WORKFLOW ARCHIVE

Plus I have the added benefit of having all my email archive stored in a format that is readable by almost any sort of digital device.Workflow Example: Text the convenience of finding emails at the speed of thought is a great one.

And granted the overhead is quite challenging. Looking at this from a purely sober perspective it looks like a lot of hoops to go through. And I don’t need to open a fully fledged client and search. This is beautifully convenient and fast, when I just want to quickly fuzzy match a subject in all of my emails and take a peak of the content. In my case the configuration files are in the ~/.mutt directory as documented here. I will rather layout some of the special custom settings that might not be documented in the guide. In this post I will not go through the details on how to configure NeoMutt. Luckily the guide online is detailed enough. It is however quite intense to configure. It is quite customizable, both in behaviour (keybindings, email handling) and look & feel. NeoMutt, which to my knowledge is based Mutt, is a wonderful email client for the command line. Again demonstrated in the aforementioned article. This also has the added benefit of having a backup client for my email.īoth Mu4e and NeoMutt use mbsync and the same email directory structure located in ~/.maildir. NeoMuttįor the rare cases I don’t have Emacs running and I just want a glance into my mailboxes I can quickly launch NeoMutt on the command line. This is extensively illustrated in this article. Emacs & mu4eĪs mentioned before I already wrote up my setup to handle emails with Emacs. Let’s take a look at the tools and programs that I user to achieve that. But how? The Toolchainįirst things first. I accomplish this with a whole host of applications, programs and add-ons. Most of my navigation is initiated by a fuzzy completion interface. In Emacs one can do this on any imaginable type of list. Granted, I noticed that the appeal is not just the text based nature of the application, but also the focus on fuzzy searching/finding. Emacs is a fantastic text based – for lack of a better word – environment.īreaking things to their basic nature takes away the distraction and it does not get any more basic than plain text. Since I started using Emacs, I have been down the rabbit hole of migrating most of my workflows into it. Then why did I switch to a text based workflow?Ī few articles ago I wrote about my obsession with Emacs. Together with Calendar.app and Contacts.app this quite a potent and well oiled machinery. It is well integrated into the OS and iCloud of course. Personally I happily used the default macOS Mail.app. Just with this selection, I am quite sure a lot of people would find their match. The following list is but a selection of some. With this comes a bunch of fantastic GUI based tools for everything – including a lot for emailing. MacOS has arguably the best looking, most succinct and most user friendly GUI in all the OS commonly used on personal computers.

Plain text workflow