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=0.2 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 9633 invoked from network); 16 Jun 2023 23:47:31 -0000 Received: from mx1.math.uh.edu (129.7.128.32) by inbox.vuxu.org with ESMTPUTF8; 16 Jun 2023 23:47:31 -0000 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.96) (envelope-from ) id 1qAJA2-00DcA4-0D for ml@inbox.vuxu.org; Fri, 16 Jun 2023 18:47:22 -0500 Received: from lists1.math.uh.edu ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.96) (envelope-from ) id 1qAJA1-001jtE-0J for ml@inbox.vuxu.org; Fri, 16 Jun 2023 18:47:21 -0500 Received: from mx2.math.uh.edu ([129.7.128.33]) by lists1.math.uh.edu with esmtp (Exim 4.96) (envelope-from ) id 1qAJ9y-001jt5-1E for ding@lists.math.uh.edu; Fri, 16 Jun 2023 18:47:18 -0500 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.96) (envelope-from ) id 1qAJ9v-00Awvj-0g for ding@lists.math.uh.edu; Fri, 16 Jun 2023 18:47:18 -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=rcn0bE2hA1v4/qQRATL07vywsVYGwMiWUkQlkggsHnw=; b=BAg7ULIjBFJzpOsZ8p1FoZXG0G f7FHTgeRhiguu0sVMaliAloQI18j/O+wyUs867//e3bM3hjHF2N9VgLXO/8q3U2ouA0I3KpbomKl/ 5oTGfDmpVW/CQKGNAMRcBFWyMIKNPduUsxeAj4cc479J8xyUzR7gzLa8tPtJLJJnSdno=; Received: from ciao.gmane.io ([116.202.254.214]) by quimby.gnus.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qAJ9m-0004cP-Ii for ding@gnus.org; Sat, 17 Jun 2023 01:47:10 +0200 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1qAJ9k-0007Tq-PC for ding@gnus.org; Sat, 17 Jun 2023 01:47:04 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: ding@gnus.org From: Andrew Cohen Subject: Re: compose new message in new frame Date: Sat, 17 Jun 2023 07:46:56 +0800 Organization: Hong Kong University of Science and Technology Message-ID: <87bkhfas27.fsf@ust.hk> References: <875y7va74h.fsf@ucl.ac.uk> <87ttvfwi2n.fsf@ust.hk> <87cz20c0xp.fsf@ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:zVlV6kBgdjtwXrfR9qFpS1eaV98= List-ID: Precedence: bulk >>>>> "ESF" == Eric S Fraga writes: ESF> On Saturday, 10 Jun 2023 at 21:41, Andrew Cohen wrote: >> You have to include the explicit config for it. For example I use >> something like this (and similar things for reply, reply-yank, >> and forward): ESF> Thank you. ESF> What you are using is what the manual suggests and I had ESF> actually tried that already. However, it doesn't work for me ESF> for some reason. What I get is that the new frame is created ESF> with the summary or group configuration and the original frame ESF> (which no longer has focus) has the message composition buffer. ESF> So basically the wrong way around. That is odd (FWIW I have been using this for years without trouble). My only guess is somehow the group and summary buffer configurations have been modified from the default so that frobbing them might not do the right thing. You might play around (although you might have already tried) with explicit configurations to see what you can control. That is, instead of using (car (cdr (assoc 'group gnus-buffer-configuration))) (and ditto for the summary configuration) just try an explicit split, for example: (gnus-add-configuration '(message (frame 1.0 (vertical 1.0 (summary 1.0)) (vertical ((user-position . t) (top . 1) (left . 1) (name . "Message")) (message 1.0 point))))) and see what happens. Does it still swap the frames? -- Andrew Cohen