From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/88837 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.gnus.general Subject: Re: What's your gnus-demon-scan-news idle time? Date: Thu, 24 Oct 2019 18:42:29 -0700 Message-ID: <877e4t7g8q.fsf@ericabrahamsen.net> References: <875zkeyd5f.fsf@dick> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="105910"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: ding@gnus.org Original-X-From: ding-owner+M37041@lists.math.uh.edu Fri Oct 25 03:43:30 2019 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from lists1.math.uh.edu ([129.7.128.208]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iNodV-000RPb-QW for ding-account@gmane.org; Fri, 25 Oct 2019 03:43:29 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.92.3) (envelope-from ) id 1iNocs-0002ww-Qr; Thu, 24 Oct 2019 20:42:50 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by lists1.math.uh.edu with esmtps (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from ) id 1iNoco-0002uE-Px for ding@lists.math.uh.edu; Thu, 24 Oct 2019 20:42:46 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92.3) (envelope-from ) id 1iNocn-0001hA-4R for ding@lists.math.uh.edu; Thu, 24 Oct 2019 20:42:46 -0500 Original-Received: from 195-159-176-226.customer.powertech.no ([195.159.176.226] helo=blaine.gmane.org) by quimby.gnus.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iNocj-0001ri-Ag for ding@gnus.org; Fri, 25 Oct 2019 03:42:43 +0200 Original-Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1iNocf-000QM9-OG for ding@gnus.org; Fri, 25 Oct 2019 03:42:37 +0200 X-Injected-Via-Gmane: http://gmane.org/ Cancel-Lock: sha1:VHic2cantwkdGlXVW7spJSxNGac= List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:88837 Archived-At: dick.r.chiang@gmail.com writes: > I am close to threading gnus-group-get-new-news and am looking for datapoints > on the following: I'm very curious to hear how you're handling threading! My observation has been that you can't (currently) run individual servers in their own threads, because they all fight over the nntp-server-buffer, and that threading the entire new-news update process basically still blocks all of emacs. How are you doing it? > 1. Do you run gnus in a separate emacs instance? > > 2. If you use gnus-demon to refresh messages, what are your TIME and IDLE > values? If you don't use gnus-demon, are you manually refreshing via "g" or > some other method? I don't do either of these. My IMAP servers are local, so there's very little lag. My NNTP server connection seems to fail by itself every eight or nine minutes, so there's exactly no lag there :) Not until I make an effort to reconnect. > For this user, I do run gnus separately from my dev work, and my > TIME is nil and IDLE is 7 minutes. After threading, I hope to swap those > settings (TIME 7, IDLE nil). Bob Newell writes: > Aloha, > > I run a single instance of emacs, and I refresh gnus only with 'g' on > a purely manual basis. But that isn't the full story. > > I use IMAP exclusively as I run gnus and emacs across something like 8 > devices. Since checking/fetching IMAP is slow and blocking, I only > want to do that when (a) I know there is something to fetch and (b) I > want to fetch it. > > When emacs starts, I have it launch a bash script that loops and > periodically checks for new mail in my IMAP boxes (primarily gmail). > If there is new mail (not just unread mail, but something newly > arrived since last check) it writes a small drop file and barks (plays > a sound). > > A small function driven off the mode-line checks the drop file. This > is very fast with no perceptible overhead. The modeline shows the > number of new emails. (A few other functions deal with updating the > mode line when I actually read the new mail.) > > So when I either hear the bark or notice new mail in the modeline, and > I feel okay with stopping my work for a bit, I make a manual check. At > this point I don't mind the blocking operation. > > Now, at least for me, NOT checking email often is a good thing. I used > to check it a lot. Maybe it's a positive feature that IMAP email > reading with gnus is both blocking and slow, because my > constant/frequent checking/reading email was an enormous time waster > and productivity drain. Now we know what your 1,000 lines of config are doing! That is a nice solution. Running a local IMAP server does a bit of the same work, in that you end up having to make a conscious decision to check your mail, but the automatic (but fairly subtle) notification is a nice touch. Eric