From: Alexander Adolf <firstname.lastname@example.org> To: Tim Visher <email@example.com> Cc: Emacs Org Mode mailing list <firstname.lastname@example.org> Subject: Re: How to use `open` to handle `message:*` links on macOS Date: Thu, 06 May 2021 19:04:51 +0200 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <CAHa53uz_R2eUe2WaLzc3MmmR6n40knk54Gq6dsa_hNiLv4O3UA@mail.gmail.com> Hello Tim, Tim Visher <firstname.lastname@example.org> writes: > [...] > I do indeed trigger the capture by switching over to Emacs and whacking my > org-capture keybinding (`C-c C`). I have a todo item that's been sitting in > my list for a very long time to figure out how to move my email habits into > emacs but I've never gotten around to it. In this case it's even worse > because the only reason I'm using Mail.app in the first place is because my > work email got moved to an Exchange server so I now don't have a good web > based interface to read mail anymore like my beloved Gmail. > > One of these days though I'm going to break the habit and move email > directly into Emacs. :) I was in the exact same situation as you until about half a year ago, which was when I decided to (finally) act on my "move email to emacs" task. Coincidentally I have recently released a blog post covering some of the basic aspects of planning the switch: https://condition-alpha.com/blog/?p=1792 IMO, a decent amount up-front planning is crucial. With notmuch, emacs's mail message handling infrastructure, and elisp, anything is possible; the sky is the limit. Email is too central to our daily work to start with the defaults and see where it takes you (IMO). So think well what your dream email workflow is, and then work towards that. The smallest, and most isolated task is perhaps configuring msmtp for sending mail; so why not start with that? Importing existing mailboxes (from Apple's mail app in my case), is another important issue (which I'll cover in a future blog post). Once you've imported some mail, you can toy around with notmuch in emacs, and the settings, until you get a gist of how things work, and how far you are from your goal. Your everyday real work is still in Apple's mail app. Once you're confident that you'll be able to survive with your emacs setup, then you can make the move, and stop using Apple's mail app. If you start a big all-in-one migration, and it fails, you're left with a big mess. Thus, doing things step-by-step with an option to revert each step if it doesn't work, is crucial, too. Hoping to have helped, --alexander
next prev parent reply other threads:[~2021-05-06 17:06 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-11 19:44 Tim Visher 2021-01-11 21:57 ` Diego Zamboni 2021-01-15 14:12 ` Alexander Adolf 2021-04-29 16:21 ` Tim Visher 2021-04-29 16:28 ` Diego Zamboni 2021-04-29 19:37 ` Tim Cross 2021-04-29 21:01 ` Tim Visher 2021-04-29 23:38 ` Alexander Adolf 2021-05-02 20:58 ` Tim Visher 2021-05-06 17:04 ` Alexander Adolf [this message] 2021-05-06 17:38 ` Tim Visher
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: How to use `open` to handle `message:*` links on macOS' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).