unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daiki Ueno <ueno@gnu.org>
Cc: 27445@debbugs.gnu.org, andrewjmoreton@gmail.com
Subject: bug#27445: 26.0.50; Insufficient documentation for pinentry.el
Date: Tue, 21 Nov 2017 17:56:19 +0200	[thread overview]
Message-ID: <83eford3rw.fsf@gnu.org> (raw)
In-Reply-To: <od13757vne6.fsf-ueno@gnu.org> (message from Daiki Ueno on Tue, 21 Nov 2017 13:15:13 +0100)

> From: Daiki Ueno <ueno@gnu.org>
> Date: Tue, 21 Nov 2017 13:15:13 +0100
> Cc: 27445@debbugs.gnu.org
> 
> Andy Moreton <andrewjmoreton@gmail.com> writes:
> 
> > How on earth is a user meant to diagnose a non-working setup without
> > adequate documentation ?
> 
> Why on earth the user could even notice the intentionally undocumented
> package, then?

I don't think we can claim that it's undocumented: it has some user
documentation in the Commentary section.

My take from this discussion is that this package will become
obsolete, but not exactly tomorrow.  So I think it would be good to
add some minimal verbiage to allow those who still need pinentry.el to
use it.  I gather the required additions are not too large.

Thanks.





  reply	other threads:[~2017-11-21 15:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-22  4:29 bug#27445: 26.0.50; Insufficient documentation for pinentry.el Michael Heerdegen
2017-10-26 12:00 ` Michael Heerdegen
2017-10-28  9:13   ` Eli Zaretskii
2017-11-18  9:50     ` Eli Zaretskii
2017-11-19  7:07       ` Daiki Ueno
2017-11-20 17:55         ` Andy Moreton
2017-11-21 12:15           ` Daiki Ueno
2017-11-21 15:56             ` Eli Zaretskii [this message]
2017-11-21 19:59               ` Daiki Ueno
2017-11-22 15:46                 ` Eli Zaretskii
2017-11-22 16:18                   ` Daiki Ueno
2017-11-23  1:06                     ` Michael Heerdegen
2017-11-23  5:08                       ` Daiki Ueno
2017-11-24  7:04                         ` Michael Heerdegen
2017-11-24 10:49                           ` Daiki Ueno
2017-11-24 13:40                             ` Eli Zaretskii
2017-11-24 15:04                               ` Daiki Ueno
2017-11-24 15:41                                 ` Eli Zaretskii
2017-11-24 17:54                             ` Richard Stallman
2017-11-20 19:33         ` Michael Heerdegen
2017-11-21  6:19           ` Daiki Ueno
2017-11-27 22:12 ` diego
2017-12-12  9:19 ` Rasmus
2017-12-22  9:49   ` Eli Zaretskii

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=83eford3rw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=27445@debbugs.gnu.org \
    --cc=andrewjmoreton@gmail.com \
    --cc=ueno@gnu.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).