Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: info-gnus-english@gnu.org
Subject: Re: Multi frame setup: get frame autodeletion?
Date: Sun, 20 Nov 2022 14:57:47 +0200	[thread overview]
Message-ID: <878rk5wzp0.fsf@thaodan.de> (raw)
In-Reply-To: <878rk6p4tf.fsf@web.de> (Michael Heerdegen's message of "Sun, 20 Nov 2022 06:34:20 +0100")

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Björn Bidar <bjorn.bidar@thaodan.de> writes:
>
>> Have you tested if you have the same issue when you just use
>> `compose-mail`  C-x m RET?
>
> I think so, but I didn't test...why do you think there should not be an
> issue - who or what would delete the frame?

I wondered because there's already a keybind to compose a new mail in a
frame C-x 5 m.

Br,

Björn




  reply	other threads:[~2022-11-20 12:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-19  2:47 Michael Heerdegen
2022-11-19 12:02 ` Björn Bidar
2022-11-20  5:34   ` Michael Heerdegen
2022-11-20 12:57     ` Björn Bidar [this message]
2022-11-19 13:13 ` Eric S Fraga
2022-11-20  5:32   ` Michael Heerdegen

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=878rk5wzp0.fsf@thaodan.de \
    --to=bjorn.bidar@thaodan.de \
    --cc=info-gnus-english@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.
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).