From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/88173 Path: news.gmane.org!.POSTED!not-for-mail From: =?utf-8?Q?R=C3=A9mi_Letot?= Newsgroups: gmane.emacs.gnus.general Subject: Re: gnorb doesn't follow up on C-c t on new messages Date: Tue, 09 Oct 2018 22:23:04 +0200 Message-ID: <87in2auaxj.fsf@sphax> References: <871s998xf7.fsf@sphax> <87sh1ot3qb.fsf@ericabrahamsen.net> <87ftxnncsm.fsf@sphax> <87in2jsye9.fsf@ericabrahamsen.net> <87lg77l8bt.fsf@sphax> <87tvlv9n40.fsf@ericabrahamsen.net> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1539116530 19751 195.159.176.226 (9 Oct 2018 20:22:10 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 9 Oct 2018 20:22:10 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: ding@gnus.org Original-X-From: ding-owner+M36387@lists.math.uh.edu Tue Oct 09 22:22:06 2018 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from lists1.math.uh.edu ([129.7.128.208]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g9yW6-00052C-Mu for ding-account@gmane.org; Tue, 09 Oct 2018 22:22:06 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.90_1) (envelope-from ) id 1g9yXT-0003XK-BH; Tue, 09 Oct 2018 15:23:31 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by lists1.math.uh.edu with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from ) id 1g9yXJ-0003UP-Ow for ding@lists.math.uh.edu; Tue, 09 Oct 2018 15:23:21 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.90_1) (envelope-from ) id 1g9yXH-0006om-5z for ding@lists.math.uh.edu; Tue, 09 Oct 2018 15:23:21 -0500 Original-Received: from [195.159.176.226] (helo=blaine.gmane.org) by quimby.gnus.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g9yXG-0002gm-0M for ding@gnus.org; Tue, 09 Oct 2018 22:23:18 +0200 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1g9yV8-0003wl-QD for ding@gnus.org; Tue, 09 Oct 2018 22:21:06 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 37 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:QyIRPUkeETWmBQsFBiWLOECCbGU= X-Spam-Score: 1.0 (+) X-Spam-Report: SpamAssassin (3.4.2 2018-09-13) analysis follows Bayesian score: 0.1917 Ham tokens: 0.000-40--1488h-0s--0d--H*M:fsf, 0.000-32--1198h-0s--0d--H*UA:Emacs, 0.000-32--1178h-0s--0d--H*u:Emacs, 0.000-31--1157h-0s--0d--reproduce, 0.000-25--940h-0s--0d--H*UA:Gnus Spam tokens: 0.997-32991--601h-26692s--0d--H*r:quimby.gnus.org, 0.995-33992--1014h-27816s--0d--HTo:D*gnus.org, 0.994-1593--52h-1307s--0d--Hx-spam-relays-external:quimby.gnus.org, 0.994-1593--52h-1307s--0d--H*RU:quimby.gnus.org, 0.993-34996--1310h-28849s--0d--Hx-spam-relays-internal:80.91.231.51 Autolearn status: no autolearn_force=no -0.0 BAYES_20 BODY: Bayes spam probability is 5 to 20% [score: 0.1917] 0.2 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail domains are different 0.8 RDNS_NONE Delivered to internal network by a host with no rDNS List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:88173 Archived-At: Eric Abrahamsen 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