From: Allen Li <darkfeline@felesatra.moe>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 36849@debbugs.gnu.org
Subject: bug#36849: 26.2; Misleading info in Gnus info about nndiary
Date: Fri, 27 Sep 2019 08:48:06 +0000 [thread overview]
Message-ID: <CADbSrJxszTuN6AQWcmVhyZ06==RtrC8TWaeKC1chpsw=xsp50A@mail.gmail.com> (raw)
In-Reply-To: <87o8zm6fmd.fsf@gnus.org>
On Sat, Sep 14, 2019 at 3:51 PM Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
> Allen Li <darkfeline@felesatra.moe> writes:
>
> > The Gnus Info manual about nndiary says this:
> >
> > (info "(gnus)Sending or Not Sending")
> >
> > • However, since ‘nndiary’ also has a ‘request-post’ method, you can
> > also use ‘C-u a’ instead of ‘C-u m’ on a diary group and the
> > message won’t actually be sent; just stored locally in the group.
> > This comes in very handy for private appointments.
> >
> > This is misleading because the "a" key for nndiary defaults to composing
> > mail (I guess because nndiary is a mail backend). This results in a
> > message that is sent, which would be undesirable for a new user who may
> > accidently mail something private.
>
> I've never used nndiary before, so I'm not sure I'm doing it right.
>
> If I
>
> `G m diary RET nndiary RET'
>
> then I get an nndiary group, and as you say, `C-u a' opens a message
> mode buffer, and if I put something in the To header, the message is
> sent to that recipient. So the documentation here is wrong -- or
> there's a bug, and `C-u a' is supposed to not send anything.
Yeah. Fixing the documentation is the most expedient. I can't say
whether the current `C-u a' behavior is a bug per se.
>
> > Instead, one must use the "S i" key to force composing a news post in
> > order to 'request-post' to the nndiary group.
>
> Hm. The "S i" key? That's not bound in my Group buffer.
Right, that's only bound in the Summary buffer. I don't think there's
a way to force posting instead of mailing from the Group buffer.
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-09-27 8:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 5:04 bug#36849: 26.2; Misleading info in Gnus info about nndiary Allen Li
2019-08-02 17:38 ` Štěpán Němec
2019-08-02 21:50 ` Allen Li
2019-09-14 15:51 ` Lars Ingebrigtsen
2019-09-27 8:48 ` Allen Li [this message]
2019-09-27 14:42 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADbSrJxszTuN6AQWcmVhyZ06==RtrC8TWaeKC1chpsw=xsp50A@mail.gmail.com' \
--to=darkfeline@felesatra.moe \
--cc=36849@debbugs.gnu.org \
--cc=larsi@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).