From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: from mx1.math.uh.edu (mx1.math.uh.edu [129.7.128.32]) by inbox.vuxu.org (Postfix) with ESMTP id 587A42407E for ; Sun, 21 Jan 2024 04:29:17 +0100 (CET) Received: from lists1.math.uh.edu ([129.7.128.208]) by mx1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1rROWJ-0000000DJg3-3Bpk for ml@inbox.vuxu.org; Sat, 20 Jan 2024 21:29:15 -0600 Received: from lists1.math.uh.edu ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.97.1) (envelope-from ) id 1rROWJ-00000003YzN-1v4t for ml@inbox.vuxu.org; Sat, 20 Jan 2024 21:29:15 -0600 Received: from mx2.math.uh.edu ([129.7.128.33]) by lists1.math.uh.edu with esmtp (Exim 4.97.1) (envelope-from ) id 1rROWG-00000003YzE-35JT for ding@lists.math.uh.edu; Sat, 20 Jan 2024 21:29:12 -0600 Received: from quimby.gnus.org ([95.216.78.240]) by mx2.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1rROW6-0000000BpZL-3fsN for ding@lists.math.uh.edu; Sat, 20 Jan 2024 21:29:12 -0600 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:Date:References: In-Reply-To:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=+4ushx3I/K/42NKRgzpyqq1Z9T9m3okyiJSoTaWKhP8=; b=Gydk46uaxiIfqEiV586WA0ZYrB 2ZMbbdNY3FPy/M9wKJEf5tto4XOJN7/vz71UtGwMqpHCQDQ2IIEE3pSScKmhjdBV4GjsGzGn+fM8k kcmUy/L7Y/USpH2ZABCi0BPrBghQHadJPfUDLlyjjsY1fuofh7dO8LYBtdG0qpAWq1PI=; Received: from mail.ericabrahamsen.net ([52.70.2.18]) by quimby.gnus.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rROVx-0006k8-Dv for ding@gnus.org; Sun, 21 Jan 2024 04:28:58 +0100 Received: from localhost (71-212-21-65.tukw.qwest.net [71.212.21.65]) (Authenticated sender: eric@ericabrahamsen.net) by mail.ericabrahamsen.net (Postfix) with ESMTPSA id 2534BFA02E; Sun, 21 Jan 2024 03:28:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericabrahamsen.net; s=mail; t=1705807730; bh=+4ushx3I/K/42NKRgzpyqq1Z9T9m3okyiJSoTaWKhP8=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=EPnk/hsmoTUsty5IpCUv8qrGoHYFjNDn799nZSz+vPPM/k04dUK+Q6dLFCaBrX/cJ aLOc3F0upt4sPLDBatEzu2fpnEy+ogutarDikyxwYLuNct+VhUsUFkdwyZfWDsNvLy mSZBZRuvzq/y7adnnTRI0Tq/TZkVYAAp5VDuLuAc= From: Eric Abrahamsen To: Michael Albinus Cc: ding@gnus.org Subject: Re: Replies, (very) wide replies, yanking, and the prefix argument In-Reply-To: <877ck4l877.fsf@gmx.de> (Michael Albinus's message of "Sat, 20 Jan 2024 09:28:44 +0100") References: <87zfx1os8a.fsf@ericabrahamsen.net> <877ck4l877.fsf@gmx.de> Date: Sat, 20 Jan 2024 19:28:48 -0800 Message-ID: <877ck3pdov.fsf@ericabrahamsen.net> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain List-ID: Precedence: bulk Michael Albinus writes: > Eric Abrahamsen writes: > > Hi Eric, > >> I'm surprised that no one hit this bug before, and I'm not sure what to >> do with it. We have "S V" (gnus-summary-very-wide-reply-with-original) >> that uses the prefix argument correctly *and* yanks message content >> correctly, so I'm not sure there's a need for "S v" to handle the prefix >> argument both ways. I suppose I could make it handle the prefix argument >> both ways, though. >> >> Let me know if anyone has any thoughts on this. > > I don't know anything about the implementation in Gnus. But as a data > point, we have also the 'S w' and 'S W' key bindings in the Summary > buffer. And 'C-u S w' seems to behave correctly. Perhaps you could > compare how those commands are implemented? I'm pretty sure I know how to fix the immediate bug here -- just replace "yank" with "current-prefix-arg" in the second call to `gnus-summary-work-articles'. The bug isn't present in "C-u S w" because the bug is specific to the "very wide" aspect of "S v". I was mostly confused about the intended behavior regarding prefix arguments provided to these commands. After looking at it a few times, I guess the point of the prefix argument for the "S v" commands is that it allows you to yank the text of the single article under point, while still using the process/prefix convention to pull in addresses from current-prefix-arg number of messages. Whereas "S V" would yank the text of all those messages, as well. I guess I'd be amazed if anyone was remembering how to use all these variants, but the rest of Gnus is like that, too, so okay! The documentation needs some fixing and clarification, though. Eric