From: Tristan Cacqueray <tdecacqu@redhat.com>
To: David Edmondson <dme@dme.org>, Leo Gaspard <leo@gaspard.io>,
notmuch@notmuchmail.org
Subject: Re: notmuch-mode and org-capture
Date: Sun, 03 Nov 2019 13:32:26 +0000 [thread overview]
Message-ID: <87o8xtdr11.tristanC@fedora> (raw)
In-Reply-To: <m21rup1gad.fsf@dme.org>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
On Sun, Nov 03, 2019 at 09:05 David Edmondson wrote:
> On Sunday, 2019-11-03 at 01:04:47 +01, Leo Gaspard wrote:
>
>> Hello,
>>
>> I have just come to notice that, when attempting to use
>> org-capture in a notmuch-tree window with a message opened in
>> the split screen below, the capture template doesn't actually
>> have the link or the various replacements that are supposed to
>> be done for the capture template, but only empty strings.
>>
>> I would assume that's due to a failure of the notmuch-tree mode
>> of setting up the appropriate org-capture hooks.
>>
>> Steps to reproduce: - z something - enter - M-x org-capture then
>> pick some template
>>
>> Do you know of a way of having such hooks?
>
> It looks as though the version of ol-notmuch.el currently in
> org-mode git has support for notmuch-tree (added in April 2019).
>
> Do you have the latest bits?
>
The org contrib lisp files got renamed earlier this year from
org-notmuch to ol-notmuch. Make sure to load the new one, for example
with use-package:
(use-package ol-notmuch :after (org notmuch))
Cheers,
-Tristan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-11-03 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 0:04 notmuch-mode and org-capture Leo Gaspard
2019-11-03 9:05 ` David Edmondson
2019-11-03 13:32 ` Tristan Cacqueray [this message]
2019-11-04 0:21 ` Leo Gaspard
2019-11-04 2:12 ` Tristan Cacqueray
2019-11-04 10:41 ` Leo Gaspard
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8xtdr11.tristanC@fedora \
--to=tdecacqu@redhat.com \
--cc=dme@dme.org \
--cc=leo@gaspard.io \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).