From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/17948 Path: news.gmane.org!not-for-mail From: Pietro Newsgroups: gmane.emacs.gnus.user Subject: Re: Gnus and gmane Date: Wed, 27 Jan 2016 23:25:39 +0000 Message-ID: <87egd24nbg.fsf@posteo.net> References: <87io2gus2g.fsf@pietrop-debian64RfL.eng.citrite.net> <87d1sob20g.fsf@debian.uxu> <8737tk82f6.fsf@posteo.net> <87h9hzamo0.fsf@debian.uxu> <871t93jnz6.fsf@pietrop-debian64RfL.eng.citrite.net> <871t93vwm9.fsf@pietrop-debian64RfL.eng.citrite.net> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1453944148 6966 80.91.229.3 (28 Jan 2016 01:22:28 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 28 Jan 2016 01:22:28 +0000 (UTC) To: info-gnus-english@gnu.org Original-X-From: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Thu Jan 28 00:26:03 2016 Return-path: Envelope-to: gegu-info-gnus-english@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aOZTM-0000HO-VW for gegu-info-gnus-english@m.gmane.org; Thu, 28 Jan 2016 00:26:01 +0100 Original-Received: from localhost ([::1]:53040 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aOZTL-0007Q9-Vo for gegu-info-gnus-english@m.gmane.org; Wed, 27 Jan 2016 18:25:59 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:32964) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aOZTI-0007O7-M1 for info-gnus-english@gnu.org; Wed, 27 Jan 2016 18:25:58 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aOZTD-0001YJ-LS for info-gnus-english@gnu.org; Wed, 27 Jan 2016 18:25:56 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:46692) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aOZTD-0001YB-Aj for info-gnus-english@gnu.org; Wed, 27 Jan 2016 18:25:51 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1aOZTA-0008WQ-Tu for info-gnus-english@gnu.org; Thu, 28 Jan 2016 00:25:48 +0100 Original-Received: from host86-179-161-220.range86-179.btcentralplus.com ([86.179.161.220]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 28 Jan 2016 00:25:48 +0100 Original-Received: from pulsarpietro by host86-179-161-220.range86-179.btcentralplus.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 28 Jan 2016 00:25:48 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 159 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: host86-179-161-220.range86-179.btcentralplus.com User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) Cancel-Lock: sha1:Y3TlHD93BW60wSYyHHd9buNeo+U= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: info-gnus-english@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader \(in English\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Original-Sender: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.gnus.user:17948 Pietro writes: > pulsarpietro@posteo.net writes: > >> Emanuel Berg writes: >> >>> Pietro writes: >>> >>>> ;; IMAP personal email >>>> (setq user-mail-address "xxxxxx@xxx.xx" >>>> user-full-name "xxxxx") >>>> (setq gnus-select-method >>>> '(nnimap "xxxx" >>>> (nnimap-stream ssl) >>>> (nnimap-address "xxxxx") >>>> (nnimap-server-port "imaps") >>>> (nnir-search-engine imap) >>>> (nnimap-expunge-on-close 'ask))) >>> >>> OK, so let's focus on Gmane and NNTP. You can comment >>> this out temporarily, enclose it in (when nil ... ), >>> or create a new .gnus and save the current one to >>> .gnus-out-of-action or whatever to bring back later >>> when Gmane works. >>> >>>> ;; Newsgroups >>>> (add-to-list 'gnus-secondary-select-methods '(nntp "news.gmane.org")) >>> >>> Looks good. >>> >>>> ;; Ordering, I wish I knew what they are about >>>> (setq gnus-extract-address-components (quote mail-extract-address-components)) >>>> (setq gnus-article-sort-functions >>>> (quote (gnus-article-sort-by-number gnus-article-sort-by-date))) >>>> (setq gnus-thread-sort-functions >>>> (quote >>>> (gnus-thread-sort-by-number gnus-thread-sort-by-most-recent-date))) >>> >>> I'd say Gnus does a good job sorting by default. >>> Especially if you don't know what they are, you can >>> comment that out at the very least until you get >>> Gmane up. >>> >>>> (custom-set-variables >>>> ;; custom-set-variables was added by Custom. >>>> ;; If you edit it by hand, you could mess it up, so be careful. >>>> ;; Your init file should contain only one such instance. >>>> ;; If there is more than one, they won't work right. >>>> '(send-mail-function (quote smtpmail-send-it)) >>>> '(smtpmail-smtp-server "xxxxxx") >>>> '(smtpmail-smtp-service 587)) >>> >>> You don't need custom to do that. This is better: >>> >>> (setq message-send-mail-function #'smtpmail-send-it) >>> >>> Note the CL-style hash quote to denote >>> a function literal. >>> >>>> (setq gnus-check-new-newsgroups nil) >>>> >>>> ;; init / fanfare / verbose >>>> (setq gnus-inhibit-startup-message t) >>>> (setq gnus-novice-user nil) >>>> (setq gnus-expert-user t) >>>> (setq gnus-interactive-exit 'quiet) >>>> (setq gnus-verbose 10) ; [0, 10] >>>> (setq gnus-verbose-backends 10) ; ditto >>> >>> That shouldn't affect your situation. You can >>> temporarily remove it just the same, just like the >>> SMTP stuff, just to do everything to isolate >>> the problem. >>> >>> Another thing to try is, instead of having NNTP and >>> Gmane as a secondary method, try to do it number one, >>> i.e.: >>> >>> (setq gnus-select-method '(nntp "news.gmane.org")) >>> >>> I've had it number one (as now) but also as >>> a secondary method, so both should work, of course, >>> but in our attempts to isolate the problem it seems >>> like a reasonable thing to do. >> No hope, my .gnus.el now contains the following : >> >> (setq gnus-select-method '(nntp "news.gmane.org")) >> >> And that is all it is there, GNUS gets stuck with the minibuffer saying: >> >> "Checking new news" forever" >> >> I can't interact with emacs at all, I can't open a toolbar menu entry >> for instance. >> >> I do not know if this has any effect but as soon as I start gnus I am >> asked for my local .authinfo.gpg password, even though I haven't setup >> anything explicitly telling GNUS use it. >> >> To make this conversation going I am manually stopping GNUS whatever it >> does with M-g and then I go through the 'gnus-group-enter-server-mode' >> and I select this group, find our article and, finally, writing a follow-up. >> >> I am not sure this helps but I was curious and I have run strace on >> the not-responding emacs instance, this is what I get : >> >> clock_gettime(CLOCK_MONOTONIC, {85650, 45181449}) = 0 >> recvmsg(8, 0x7ffe93c2de30, 0) = -1 EAGAIN (Resource temporarily unavailable) >> poll([{fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=11, >> events=POLLIN}, {fd=5, events=POLLIN}], 4, 0) = 0 (Timeout) >> clock_gettime(CLOCK_MONOTONIC, {85650, 45317695}) = 0 >> clock_gettime(CLOCK_REALTIME, {1453891059, 902641062}) = 0 >> clock_gettime(CLOCK_REALTIME, {1453891059, 902675691}) = 0 >> clock_gettime(CLOCK_REALTIME, {1453891059, 902708950}) = 0 >> pselect6(15, [5 7 8 11 14], [], NULL, {0, 9965371}, {NULL, 8}) = 0 (Timeout) >> clock_gettime(CLOCK_MONOTONIC, {85650, 55595850}) = 0 >> recvmsg(8, 0x7ffe93c2de30, 0) = -1 EAGAIN (Resource temporarily unavailable) >> poll([{fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=11, >> events=POLLIN}, {fd=5, events=POLLIN}], 4, 0) = 0 (Timeout) >> clock_gettime(CLOCK_MONOTONIC, {85650, 55783461}) = 0 >> clock_gettime(CLOCK_REALTIME, {1453891059, 913131581}) = 0 >> clock_gettime(CLOCK_REALTIME, {1453891059, 913188508}) = 0 >> clock_gettime(CLOCK_REALTIME, {1453891059, 913231684}) = 0 >> pselect6(15, [5 7 8 11 14], [], NULL, {0, 9943073}, {NULL, 8}) = 0 (Timeout) >> clock_gettime(CLOCK_MONOTONIC, {85650, 66134187}) = 0 >> recvmsg(8, 0x7ffe93c2de30, 0) = -1 EAGAIN (Resource temporarily unavailable) >> poll([{fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=11, >> events=POLLIN}, {fd=5, events=POLLIN}], 4, 0) = 0 (Timeout) >> clock_gettime(CLOCK_MONOTONIC, {85650, 66299517}) = 0 >> clock_gettime(CLOCK_REALTIME, {1453891059, 923649141}) = 0 >> clock_gettime(CLOCK_REALTIME, {1453891059, 923689728}) = 0 >> clock_gettime(CLOCK_REALTIME, {1453891059, 923728795}) = 0 >> pselect6(15, [5 7 8 11 14], [], NULL, {0, 9959413}, {NULL, 8}) = 0 (Timeout) >> clock_gettime(CLOCK_MONOTONIC, {85650, 76648247}) = 0 >> recvmsg(8, 0x7ffe93c2de30, 0) = -1 EAGAIN (Resource temporarily unavailable) >> poll([{fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=11, >> events=POLLIN}, {fd=5, events=POLLIN}], 4, 0) = 0 (Timeout) >> clock_gettime(CLOCK_MONOTONIC, {85650, 76789593}) = 0 >> clock_gettime(CLOCK_REALTIME, {1453891059, 934117273}) = 0 >> clock_gettime(CLOCK_REALTIME, {1453891059, 934151649}) = 0 >> clock_gettime(CLOCK_REALTIME, {1453891059, 934187433}) = 0 >> pselect6(15, [5 7 8 11 14], [], NULL, {0, 9965624}, {NULL, 8}) = 0 (Timeout) >> clock_gettime(CLOCK_MONOTONIC, {85650, 87054215}) = 0 >> recvmsg(8, 0x7ffe93c2de30, 0) = -1 EAGAIN (Resource temporarily unavailable) >> poll([{fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=11, >> events=POLLIN}, {fd=5, events=POLLIN}], 4, 0) = 0 (Timeout) >> clock_gettime(CLOCK_MONOTONIC, {85650, 87175745}) = 0 >> clock_gettime(CLOCK_REALTIME, {1453891059, 944489275}) = 0 >> clock_gettime(CLOCK_REALTIME, {1453891059, 944522317}) = 0 >> clock_gettime(CLOCK_REALTIME, {1453891059, 944555567}) = 0 >> pselect6(15, [5 7 8 11 14], [], NULL, {0, 9966958}, {NULL, 8}^CProcess 28307 detached > > All solved, the reason why it all looked fairly unreasonable was > because of some rubbish state being saved into the .news.eld and .news > files. Once removed then you instructions worked smoothly. > > Thanks a lot. Is there anything specific I need to do to get threads in date order ?