From: rameiko87@posteo.net
To: Eli Zaretskii <eliz@gnu.org>
Cc: 69738@debbugs.gnu.org
Subject: bug#69738: Followup
Date: Mon, 15 Apr 2024 10:15:55 +0000 [thread overview]
Message-ID: <4d7b2d2317ad9512628fbd2725f33d8b@posteo.net> (raw)
In-Reply-To: <867cgzn5jw.fsf@gnu.org>
> So please show a minimal
> recipe for reproducing this, after applying the patch I sent, and
> starting from "emacs -Q -nw". There's probably something I'm missing.
emacs -nw -Q (FRAME 1 IS SCRATCH)
C-x 5 2
M-x load-file PATCH
M-x rmail (FRAME 2 IS RMAIL)
M-: (setq rmail-mail-new-frame t)
C-x 5 2
C-x b *Messages* (FRAME 3 IS MESSAGES)
C-x 5 o (BACK TO FRAME 2)
m (NEW MAIL OPENS ON FRAME 4)
C-u - C-x 5 o (THIS IS WHAT THE PATCH DOES, REVERTING BACK TO FRAME 1
WHICH IS SCRATCH AND NOT RMAIL)
Does it make sense?
Curiously, replacing the last line by C-c C-k kills the draft but
doesn't change the frame (note that I applied the patch). I deduce that
rmail-mail-return is not called by C-c C-k... Am I doing something
wrong?
next prev parent reply other threads:[~2024-04-15 10:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 22:49 bug#69738: [BUG] rmail-mail-new-frame doesn't delete the new frame after composing the message on Emacs 29.2 rameiko87
2024-03-12 13:54 ` Eli Zaretskii
2024-03-21 8:57 ` Eli Zaretskii
2024-04-13 17:44 ` bug#69738: Followup rameiko87
2024-04-14 9:44 ` Eli Zaretskii
2024-04-14 16:14 ` rameiko87
2024-04-14 16:30 ` Eli Zaretskii
2024-04-14 17:47 ` rameiko87
2024-04-14 17:55 ` rameiko87
2024-04-14 18:50 ` Eli Zaretskii
2024-04-14 18:49 ` Eli Zaretskii
2024-04-15 10:15 ` rameiko87 [this message]
2024-04-20 11:11 ` Eli Zaretskii
2024-05-04 9:37 ` Eli Zaretskii
2024-05-06 19:12 ` rameiko87
2024-05-12 22:42 ` rameiko87
2024-05-13 10:53 ` Eli Zaretskii
2024-05-28 13:28 ` rameiko87
2024-06-20 9:58 ` Eli Zaretskii
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=4d7b2d2317ad9512628fbd2725f33d8b@posteo.net \
--to=rameiko87@posteo.net \
--cc=69738@debbugs.gnu.org \
--cc=eliz@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.