From: pulsarpietro@posteo.net
To: info-gnus-english@gnu.org
Subject: Re: Gnus and gmane
Date: Wed, 27 Jan 2016 04:50:05 -0600 [thread overview]
Message-ID: <871t93jnz6.fsf@pietrop-debian64RfL.eng.citrite.net> (raw)
In-Reply-To: <87h9hzamo0.fsf@debian.uxu>
Emanuel Berg <embe8573@student.uu.se> writes:
> Pietro <pulsarpietro@posteo.net> 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
next prev parent reply other threads:[~2016-01-27 10:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 18:13 Pietro
2016-01-26 18:59 ` Emanuel Berg
2016-01-26 21:18 ` Pietro
2016-01-27 0:30 ` Emanuel Berg
2016-01-27 10:50 ` pulsarpietro [this message]
2016-01-27 16:02 ` Pietro
2016-01-27 23:25 ` Pietro
2016-01-29 3:01 ` Emanuel Berg
-- strict thread matches above, loose matches on Subject: below --
2003-11-01 7:45 gnus " Simon András
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=871t93jnz6.fsf@pietrop-debian64RfL.eng.citrite.net \
--to=pulsarpietro@posteo.net \
--cc=info-gnus-english@gnu.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).