From: Brett Presnell <presnell@member.fsf.org>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Can't store link in mu4e
Date: Sun, 04 Sep 2016 16:02:16 -0400 [thread overview]
Message-ID: <877farjuwn.fsf@ufl.edu> (raw)
In-Reply-To: <87fupk3kee.fsf@ufl.edu>
After looking into this more carefully, I learned that org-add-link-type
is deprecated. In case anyone else runs into this, the solution is to
edit org-mu4e.el, replacing the lines
(org-add-link-type "mu4e" 'org-mu4e-open)
(add-hook 'org-store-link-functions 'org-mu4e-store-link)
with the single line
(org-link-set-parameters "mu4e" :follow #'org-mu4e-open :store #'org-mu4e-store-link)
I'll report this to the mu developer in case he isn't already aware of
the upcoming change in org mode. I wonder if org-mu4e.el wouldn't be
better maintained as a part of org (like org-gnus.el and org-mew.el)
rather than as a part of mu4e.
Brett Presnell <presnell@member.fsf.org> writes:
> I pulled the latest org from git a few days ago. Now I can no longer
> store links to email messages in mu4e with "C-c l". The message I get
> is
>
> No method for storing a link from this buffer
>
> Nothing else has changed, and I am still able to pull up email message
> by clicking on (old) links in org files, and org-capture of email
> messages still works with "C-c c".
>
> I'm running
>
> mu/mu4e version 0.9.17 from github
>
> and a snapshot of GNU Emacs 25
>
> GNU Emacs 25.1.50.2 (x86_64-pc-linux-gnu, GTK+ Version 3.18.9) of
> 2016-08-23
>
> Any ideas? I really depend on this functionality.
next prev parent reply other threads:[~2016-09-04 20:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 17:42 Can't store link in mu4e Brett Presnell
2016-09-04 20:02 ` Brett Presnell [this message]
2016-09-05 15:51 ` Nicolas Goaziou
2016-09-05 19:39 ` Brett Presnell
-- strict thread matches above, loose matches on Subject: below --
2016-08-29 16:03 Brett Presnell
2016-08-29 17:11 ` Michael Welle
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=877farjuwn.fsf@ufl.edu \
--to=presnell@member.fsf.org \
--cc=emacs-orgmode@gnu.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public 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).