From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: problems with gcc
Date: Tue, 12 Jan 2021 14:30:21 +0100 [thread overview]
Message-ID: <87h7nme102.fsf@mat.ucm.es> (raw)
In-Reply-To: <87v9c275d5.fsf@zoho.eu>
[-- Attachment #1: Type: text/plain, Size: 242 bytes --]
> Uwe Brauer wrote:
> ... why not?
> Don't you expect `message-news-p' to be true after
> `gnus-summary-post-news'?
> Well, it is anyway. You know, news ... news :)
I tried gnus-summary-mail-other-window and it shows the same behavior.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2021-01-12 13:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 8:14 Uwe Brauer
2021-01-12 11:37 ` Emanuel Berg
2021-01-12 13:28 ` Uwe Brauer
2021-01-12 17:52 ` Emanuel Berg
2021-01-13 18:50 ` Uwe Brauer
2021-01-12 13:30 ` Uwe Brauer [this message]
2021-01-12 13:53 ` Adam Sjøgren
2021-01-12 15:56 ` Uwe Brauer
2021-01-12 16:05 ` Uwe Brauer
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=87h7nme102.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--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).