Gnus development mailing list
 help / color / mirror / Atom feed
From: "Rémi Letot" <hobbes@poukram.net>
To: ding@gnus.org
Subject: Re: gnorb doesn't follow up on C-c t on new messages
Date: Tue, 09 Oct 2018 22:23:04 +0200	[thread overview]
Message-ID: <87in2auaxj.fsf@sphax> (raw)
In-Reply-To: <87tvlv9n40.fsf@ericabrahamsen.net>

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

>>
>>> If that's in there, I don't know what else could be going wrong. If you
>>> didn't have `gnorb-gnus-new-todo-capture-key' set, you'd get an error.
>>> Otherwise, there's nothing to stop you arriving at the call to
>>> org-capture...
>>
>> gnorb-gnus-new-todo-capture-key was not set, but I didn't get an
>> error.

I tried again, I don't have any error. Nothing in the minibuffer, and
nothing in *Messages*

> Well that's weird, if it was nil the function should have blown up.

No explosion to report :-)

>> Now I have set it:
>>
>> (setq gnorb-gnus-new-todo-capture-key 't)
>
> That should be the string "t", to match the key in your capture
> templates.

AHA, now I do have a buried capture buffer that I can fill and file.

So if you have a fix pending for the fact that the buffer is buried,
I can live with that until the fix makes it to elpa.

Thanks a lot for that package and your help, don't hesitate to ask if
you need more information on my particular setup or any help to
reproduce «my» bugs.

Thanks,
-- 
Rémi




  reply	other threads:[~2018-10-09 20:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-01 16:05 Rémi Letot
2018-10-02 21:53 ` Eric Abrahamsen
2018-10-02 23:34   ` Rémi Letot
2018-10-02 23:48     ` Eric Abrahamsen
2018-10-09 10:31       ` Rémi Letot
2018-10-09 15:05         ` Eric Abrahamsen
2018-10-09 20:23           ` Rémi Letot [this message]
2018-10-09 21:23             ` Eric Abrahamsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87in2auaxj.fsf@sphax \
    --to=hobbes@poukram.net \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).