From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: gnorb doesn't follow up on C-c t on new messages
Date: Tue, 02 Oct 2018 16:48:46 -0700 [thread overview]
Message-ID: <87in2jsye9.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87ftxnncsm.fsf@sphax>
Rémi Letot <hobbes@poukram.net> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>
>> Thanks for the further reports.
>
> no problem, I want it to work :-)
>
>> Can you check to see if the Org capture buffer is simply getting buried
>> during this process? Ie, is there a pending capture buffer hiding
>> somewhere in your buffer list?
>>
>> If so, and if you hit "C-c C-c" in that buffer, to finalize the capture,
>> does it give you a "Selecting deleted buffer" error?
>>
>> Hopefully both of those things are true, as I have fixes for both of
>> them!
>
> alas, I don't have a buried Org capture buffer. The message is sent, and
> nothing else happens. I restarted my emacs just to be sure, because I
> tend to have lots of buffers after a while, but there is no capture
> buffer.
Well, that's unfortunate. It should very clearly call org-capture after
the message is sent. When you're composing the message, after you run
C-c t, can you check the value of `message-send-actions' and confirm
that it contains the symbol `gnorb-gnus-outgoing-make-todo-1'?
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...
Can you show me the template that's pointed to by
`gnorb-gnus-new-todo-capture-key'?
Thanks,
Eric
next prev parent reply other threads:[~2018-10-02 23:48 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 [this message]
2018-10-09 10:31 ` Rémi Letot
2018-10-09 15:05 ` Eric Abrahamsen
2018-10-09 20:23 ` Rémi Letot
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=87in2jsye9.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.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).