Re: gnorb doesn't follow up on C-c t on new messages

[Eric Abrahamsen <eric@ericabrahamsen.net>]

Rémi Letot <hobbes@poukram.net> writes:

> 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.

Yup, I see the same thing, and I'll push a fix for this in the next
couple of days.

> 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.

Once this is done, I think we will have fixed all your bugs! But please
do continue to report.

Thanks,
Eric