From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, FREEMAIL_FROM,RCVD_IN_DNSWL_MED autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 16181 invoked from network); 20 Aug 2020 03:37:48 -0000 Received: from lists1.math.uh.edu (129.7.128.208) by inbox.vuxu.org with ESMTPUTF8; 20 Aug 2020 03:37:48 -0000 Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.94) (envelope-from ) id 1k8bOJ-008Zl2-9A; Wed, 19 Aug 2020 22:37:27 -0500 Received: from mx1.math.uh.edu ([129.7.128.32]) by lists1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from ) id 1k8bOE-008Ziv-9k for ding@lists.math.uh.edu; Wed, 19 Aug 2020 22:37:22 -0500 Received: from quimby.gnus.org ([95.216.78.240]) by mx1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from ) id 1k8bOB-00EGVX-I9 for ding@lists.math.uh.edu; Wed, 19 Aug 2020 22:37:21 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:Mime-Version:References:Message-ID:Date:Subject: From:To:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=Ff+l2hilZuzSJ5AKEHZVEdaEiYCwS6MsjJVMuhzg+0c=; b=ELrtwmimJ5W7e07r+wzGOouTOH sqguhaCNQ1zAZ/L8UbIe6QcmPV5a9OXLJRPhD22ZEqqJ2BH2BCQU4x2hvxSq+NIf1BltxPXDhNZDF aa47E+EUrhSpPZGxmNqMZIEFWaiRWaQH/wjLJee5PDEh+Hx5kXWQQX7bn2HsHBlfq6G8=; Received: from static.214.254.202.116.clients.your-server.de ([116.202.254.214] helo=ciao.gmane.io) by quimby with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k8bNw-0006wG-O1 for ding@gnus.org; Thu, 20 Aug 2020 05:37:14 +0200 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1k8bNw-0007A0-1a for ding@gnus.org; Thu, 20 Aug 2020 05:37:04 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: ding@gnus.org From: Wayne Harris Subject: Re: on a buffer performance test on GNU EMACS 28 Date: Thu, 20 Aug 2020 00:36:21 -0300 Message-ID: <86eeo2vvii.fsf@protonmail.com> References: <861rk7xs1n.fsf@protonmail.com> <871rk6ijxu.fsf@ericabrahamsen.net> <86eeo57wly.fsf@protonmail.com> <86tuwzz936.fsf@protonmail.com> <878sead2ih.fsf@ericabrahamsen.net> <86364i2gzl.fsf@rafikhan.io> <87y2ma9g0k.fsf@ericabrahamsen.net> Mime-Version: 1.0 Content-Type: text/plain Cancel-Lock: sha1:dERFfydKa6C5h3IID0QbV1bu+Tw= List-ID: Precedence: bulk Eric Abrahamsen writes: > On 08/19/20 22:22 PM, Rafi Khan wrote: >> Eric Abrahamsen writes: >>> To my embarrassment, I don't know how it works, either. I use Gnus as a >>> newsreader, and access these emacs.* groups via nntp. But sometimes I >>> followup using "F", and sometimes I reply with "S W". I'm often not even >>> aware of which I've used. In the latter case, I must be sending email to >>> ding@gnus.org, but it all ends up looking the same to me. >> >> I never really understood the difference between "F" and "S W"... could >> you explain? By the way, Rafi Khan's message must have gone only to your mailbox because it did not reach the newsgroup (so I think it did not reach the mail list either). [...] > Where I'm less certain is what happens when you mail reply in an nntp > newsgroup. This doesn't happen. The headers are wrecking havoc in your mind. :-) You can't mail reply in NNTP newsgroup. You can post an NNTP message with a header such as ``To: ding@somewhere.com''. That's no problem. By having such header, someone reading the NNTP server could use their NNTP client to reply by mail if they so wished. Now, because the NNTP server will handle your message to some system that will make it post to the mail list, then the list needs all the mail headers that the mail list mechanism will require. That's why we end up with messages that look like NNTP articles and SMTP messages. That's my theory. > In the case of gnus.general, the address "ding@gnus.org" is always in > the cc, so if you do any of the (very) wide reply options, Gnus > apparently knows that your message will also go to the group, and it > lets you send the mail reply (as opposed to the news followup). If you > try a non-wide mail reply (which would not go to the group) it assumes > you're making a dumb mistake and asks for confirmation. > > I don't know how much of this is standard nntp stuff, how much > particular to Gnus the newsreader, and how much particular to > gnus.general the newsgroup. I think essentially nothing is particular to NNTP nor to Gnus. The designers of this system are using their freedom to add headers to messages to make this marvelous NNTP way to participate in mail lists. It's a very great contribution --- thanks to Gmane! > Hope that didn't make things worse! It's all good either way. I hope someone educates us if we're too off the right course.