Gnus development mailing list
 help / color / mirror / Atom feed
From: Felix Natter <fnatter@gmx.net>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: ding@gnus.org
Subject: Re: compose new message in new frame
Date: Sat, 10 Jun 2023 15:03:15 +0200	[thread overview]
Message-ID: <87ilbvmpv0.fsf@bitburger.home.felix> (raw)
In-Reply-To: <875y7va74h.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Sat, 10 Jun 2023 12:28:46 +0100")

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

[..]

hello Eric,

just a note, may or may not hit you: I ran into a bug where the Gcc:
header is not generated (and thus the mail is not archived) if you
compose a mail from a secondary frame (C-x 5 m or C-x 5 2, then m):

  https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62345

Best Regards,
Felix
--
Felix Natter
debian/rules!


  reply	other threads:[~2023-06-10 13:03 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 [this message]
2023-06-12 12:32   ` Eric S Fraga
2023-06-10 13:41 ` Andrew Cohen
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=87ilbvmpv0.fsf@bitburger.home.felix \
    --to=fnatter@gmx.net \
    --cc=ding@gnus.org \
    --cc=e.fraga@ucl.ac.uk \
    /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).