Gnus development mailing list
 help / color / mirror / Atom feed
From: Andrew Cohen <acohen@ust.hk>
To: ding@gnus.org
Subject: Re: compose new message in new frame
Date: Sat, 10 Jun 2023 21:41:20 +0800	[thread overview]
Message-ID: <87ttvfwi2n.fsf@ust.hk> (raw)
In-Reply-To: <875y7va74h.fsf@ucl.ac.uk>

>>>>> "ESF" == Eric S Fraga <e.fraga@ucl.ac.uk> writes:

    ESF> I currently have gnus configured (using gnus-add-configuration)
    ESF> as follows: (gnus-add-configuration '(message (frame 1.0
    ESF> (vertical (message 1.0 point)))))

    ESF> (elided, hopefully correctly, to the minimal bits as the body
    ESF> is actually a cond which changes the behaviour depending on the
    ESF> monitor size)

    ESF> This does bring up a frame with the composition buffer but the
    ESF> original frame also shows the same buffer, not the (say)
    ESF> summary and article that I was reading.

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):

(gnus-add-configuration
 '(message
   (frame 1.0
          (if (not (buffer-live-p gnus-summary-buffer))
              (car (cdr (assoc 'group gnus-buffer-configuration)))
            (car (cdr (assoc 'summary gnus-buffer-configuration))))
          (vertical ((user-position . t) (top . 1) (left . 1)
                     (name . "Message"))
                    (message 1.0 point)))))

(You also might want to kill the frame afterwards:

(add-hook 'gnus-message-setup-hook
	  (lambda ()
	    (message-add-action #'delete-frame 'exit 'postpone 'kill)))

-- 
Andrew Cohen



  parent reply	other threads:[~2023-06-10 13:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-10 11:28 Eric S Fraga
2023-06-10 13:03 ` Felix Natter
2023-06-12 12:32   ` Eric S Fraga
2023-06-10 13:41 ` Andrew Cohen [this message]
2023-06-12 12:36   ` Eric S Fraga
2023-06-16 23:46     ` Andrew Cohen
2023-06-19  8:58       ` Eric S Fraga

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ttvfwi2n.fsf@ust.hk \
    --to=acohen@ust.hk \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).