all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Štěpán Němec" <stepnem@gmail.com>
To: Allen Li <darkfeline@felesatra.moe>
Cc: 36849@debbugs.gnu.org
Subject: bug#36849: 26.2; Misleading info in Gnus info about nndiary
Date: Fri, 02 Aug 2019 19:38:19 +0200	[thread overview]
Message-ID: <87k1bvcvsk.fsf@gmail.com> (raw)
In-Reply-To: <805znk5czq.fsf@felesatra.moe> (Allen Li's message of "Mon, 29 Jul 2019 22:04:57 -0700")

On Mon, 29 Jul 2019 22:04:57 -0700
Allen Li wrote:

> 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.
>
> Instead, one must use the "S i" key to force composing a news post in
> order to 'request-post' to the nndiary group.

I don't use nndiary, but the way you describe this makes me wonder if it
is a misunderstanding.

Are you sure you tried 'C-u a' in the *Group* buffer? Note the
instructions say _on_ (i.e., in the *Group* buffer with point on the
group), not _in_ the diary group. IMO it should work as described. Also,
there is not even a "S i" binding in the *Group* buffer, whereas there
is one in the *Summary* buffer (i.e., when you enter the group), which
reinforces my suspicion.

-- 
Štěpán





  reply	other threads:[~2019-08-02 17:38 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 [this message]
2019-08-02 21:50   ` Allen Li
2019-09-14 15:51 ` Lars Ingebrigtsen
2019-09-27  8:48   ` Allen Li
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k1bvcvsk.fsf@gmail.com \
    --to=stepnem@gmail.com \
    --cc=36849@debbugs.gnu.org \
    --cc=darkfeline@felesatra.moe \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.