From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: problems with gcc
Date: Wed, 13 Jan 2021 19:50:01 +0100 [thread overview]
Message-ID: <87bldswu1y.fsf@mat.ucm.es> (raw)
In-Reply-To: <87bldu6o0t.fsf@zoho.eu>
[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]
>>> "EB" == Emanuel Berg <moasenwood@zoho.eu> writes:
> Uwe Brauer wrote:
>>> Don't you expect `message-news-p' to be true after
>>> `gnus-summary-post-news'?
>>>
>>> Well, it is anyway. You know, news ... news :)
>>
>> But why then to have if?
> It is so to have different archives for news and mails, as
> you know.
> I don't like that, I like it to be the same, interface and
> archive and everything, at least everything on my end of
> things, so I do
> (setq message-default-news-headers "To: ")
> (setq message-default-mail-headers "Newsgroups: ")
> (setq gnus-gcc-mark-as-read t)
> (setq gnus-message-archive-group "nnml:mail.sent")
> then send with
> (gnus-post-news 'post "") ; [1]
>> Ok then which command should I use to send, hm, mail?
> `compose-mail' ?
> But again I think it makes more sense to have the same
> interface and then let the content of the headers decide if it
> is news, mail, or both.
>> I mean I want one GCC for mail and one for newsgroups.
> Yes, and you should be on the right track :)
> [1] new-message, line 54 in
> https://dataswamp.org/~incal/emacs-init/gnus/gnus-my.el
Interesting thanks.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2021-01-13 18:50 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 [this message]
2021-01-12 13:30 ` Uwe Brauer
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=87bldswu1y.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).