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 1933 invoked from network); 10 Jun 2023 11:29:10 -0000 Received: from mx1.math.uh.edu (129.7.128.32) by inbox.vuxu.org with ESMTPUTF8; 10 Jun 2023 11:29:10 -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 1q7wmJ-008wOH-2t for ml@inbox.vuxu.org; Sat, 10 Jun 2023 06:29:07 -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 1q7wmJ-001Ufs-01 for ml@inbox.vuxu.org; Sat, 10 Jun 2023 06:29:07 -0500 Received: from mx1.math.uh.edu ([129.7.128.32]) by lists1.math.uh.edu with esmtp (Exim 4.96) (envelope-from ) id 1q7wmG-001Ufj-1I for ding@lists.math.uh.edu; Sat, 10 Jun 2023 06:29:04 -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.96) (envelope-from ) id 1q7wmE-008wNj-0W for ding@lists.math.uh.edu; Sat, 10 Jun 2023 06:29:04 -0500 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: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:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=7gxV2iSLPvsQxMZXVwrlg2hjay/GD4ZlNwbys/fIa0k=; b=HXlhbzpGvwaDsqC9oKa+A/IPLc JwcVtGQhPS/6E9sILcRsflxnsooN9JkK1o5iL6th3R//3T5U4pkfIlu0tnTW2GIhRqi41XJubrRc8 nGM6xTO9y0TxcMsvt++oZpHymfdAY34AyT9+w0iXjaOhyP/EfkWQ3iyx6FhThKVaX5tE=; 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 1q7wm5-00013W-Dd for ding@gnus.org; Sat, 10 Jun 2023 13:28:56 +0200 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1q7wm3-0000a8-Hx for ding@gnus.org; Sat, 10 Jun 2023 13:28:51 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: ding@gnus.org From: Eric S Fraga Subject: compose new message in new frame Date: Sat, 10 Jun 2023 12:28:46 +0100 Organization: On the Interweb somewhere Message-ID: <875y7va74h.fsf@ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain User-Agent: gnus (Emacs 30.0.50) Cancel-Lock: sha1:UpdbNCtteEXw6PzhW8r96zOxU4g= X-Url: http://www.ucl.ac.uk/~ucecesf/ List-ID: Precedence: bulk I currently have gnus configured (using gnus-add-configuration) as follows: --8<---------------cut here---------------start------------->8--- (gnus-add-configuration '(message (frame 1.0 (vertical (message 1.0 point))))) --8<---------------cut here---------------end--------------->8--- (elided, hopefully correctly, to the minimal bits as the body is actually a cond which changes the behaviour depending on the monitor size) This does bring up a frame with the composition buffer but the original frame also shows the same buffer, not the (say) summary and article that I was reading. The documentation, although quite extensive, doesn't tell me how to ensure the original frame stays as it is/was before asking to compose a new message. Any suggestions welcome! Thank you, eric -- Eric S Fraga via gnus (Emacs 30.0.50 2023-05-02) on Debian 11.6