From: Tim Visher <firstname.lastname@example.org> To: Alexander Adolf <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, 6 May 2021 13:38:12 -0400 [thread overview] Message-ID: <CAHa53uye-+PeR_DnqKzUqinAwMx6ssqe8988kZFd=sh42xyoaQ@mail.gmail.com> (raw) In-Reply-To: <email@example.com> [-- Attachment #1: Type: text/plain, Size: 1008 bytes --] On Thu, May 6, 2021 at 1:04 PM Alexander Adolf < firstname.lastname@example.org> wrote: > > Tim Visher <email@example.com> writes: > > > [...] > > > > 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 > > … > > The smallest, and most isolated task is perhaps configuring msmtp for > sending mail; so why not start with that? > > … > > 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. > Great advice and info all around! Thanks so much. :) [-- Attachment #2: Type: text/html, Size: 1548 bytes --]
prev parent reply other threads:[~2021-05-06 17:48 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 2021-05-06 17:38 ` Tim Visher [this message]
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 \ --in-reply-to='CAHa53uye-+PeR_DnqKzUqinAwMx6ssqe8988kZFd=sh42xyoaQ@mail.gmail.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).