From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/18854 Path: news.gmane.org!.POSTED!not-for-mail From: Robert Girault Newsgroups: gmane.emacs.gnus.user Subject: Re: on automatic gnus-summary-insert-new-articles after posting Date: Sun, 29 Jul 2018 13:00:58 -0300 Organization: Aioe.org NNTP Server Message-ID: <86va8yni9x.fsf@dev.null> References: <86d0v7jrvd.fsf@dev.null> <8636w2hp1b.fsf@dev.null> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1532880186 27608 195.159.176.226 (29 Jul 2018 16:03:06 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 29 Jul 2018 16:03:06 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (windows-nt) To: info-gnus-english@gnu.org Original-X-From: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Sun Jul 29 18:03:02 2018 Return-path: Envelope-to: gegu-info-gnus-english@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fjo9u-00077H-3X for gegu-info-gnus-english@m.gmane.org; Sun, 29 Jul 2018 18:03:02 +0200 Original-Received: from localhost ([::1]:48939 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fjoC0-0004Wo-RZ for gegu-info-gnus-english@m.gmane.org; Sun, 29 Jul 2018 12:05:12 -0400 X-Received: by 2002:a1c:e714:: with SMTP id e20-v6mr1453321wmh.31.1532880062534; Sun, 29 Jul 2018 09:01:02 -0700 (PDT) X-FeedAbuse: http://nntpfeed.proxad.net/abuse.pl feeded by 78.192.65.63 Original-Path: usenet.stanford.edu!h7-v6no6638936wmb.0!news-out.google.com!s23-v6ni24425wmc.0!nntp.google.com!proxad.net!feeder1-2.proxad.net!nntpfeed.proxad.net!news.muarf.org!news.gegeweb.eu!gegeweb.org!aioe.org!.POSTED!not-for-mail Original-Newsgroups: gnu.emacs.gnus Original-Lines: 49 Original-NNTP-Posting-Host: Ovf+arS3XaapLdMoy7A3Ug.user.gioia.aioe.org Original-X-Complaints-To: abuse@aioe.org Cancel-Lock: sha1:LbwL7ZQhHf4YMvx5G2xfnf4lFhE= X-Gnus-Delayed: Wed, 01 Aug 2018 12:48:52 -0300 X-Notice: Filtered by postfilter v. 0.8.3 Original-Xref: usenet.stanford.edu gnu.emacs.gnus:89797 X-BeenThere: info-gnus-english@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.gnus.user:18854 Archived-At: Eric Abrahamsen writes: > Robert Girault writes: > > [...] > >> This brings me to a point I've been trying to set up Gnus for. I'd like >> to keep, for a while, a history of everything I wrote. Saving messages >> locally isn't good enough because the context is gone. The context is >> the thread. >> >> When I enter a group, I feel lost. I think it's slrn that I've used in >> the past. When I'd enter a news group, I'd have a clear idea of what's >> happening---which threads are growing and which are not. > > I looked up slrn, and interestingly the author seemed to have written it > because he found Gnus too slow! I can't compare it myself. I run them on different systems. > I don't know how slrn does it, so I don't know exactly what effect > you're after. Are you using threading? I've got `gnus-show-threads' set > to t and `gnus-fetch-old-headers' set to 'some, and that shows me just > as much context as I want. Surprisingly perhaps, I feel better without threading, so I turned it off. When I wanna see a parent message, I say ^. >> Also, my way of working is to write articles, but only post them after >> I've reviewed them. I haven't yet acquired skills enough to do that >> with Gnus. >> >> I know it's possible to save them as drafts and send them later, but I'd >> like to distinguish between partially written messages from messages >> queued for delivery. > > You can use the agent for this. When you're finished with a message, hit > "C-c C-j" (gnus-delay-article), and you can choose a future date at > which the message will send. It won't actually send at that date unless > you run the `gnus-delay-send-queue' command in the *Group* buffer. That > might do what you want, though I don't know how easy it is to edit > messages once you've added them to the queue. The manual says it will send if I check for new messages, but I'm thinking I must run gnus-delay-initialize. I won't turn it on for now. I'm getting there. Thanks! [...]