From: Michael Heerdegen <michael_heerdegen@web.de>
To: Daiki Ueno <ueno@gnu.org>
Cc: 27445@debbugs.gnu.org
Subject: bug#27445: 26.0.50; Insufficient documentation for pinentry.el
Date: Fri, 24 Nov 2017 08:04:50 +0100 [thread overview]
Message-ID: <87y3mww419.fsf@web.de> (raw)
In-Reply-To: <87lgixvayl.fsf-ueno@gnu.org> (Daiki Ueno's message of "Thu, 23 Nov 2017 06:08:18 +0100")
Daiki Ueno <ueno@gnu.org> writes:
> Use it at your own risk or blame someone else
> [...]
> I am almost done with this issue.
If you say it makes no sense to document that stuff, I can't argue
against that. Sorry if you feel blamed (actually I didn't blame anyone)
- but if this is to be "used at own risk" and not worth or possible to
be documented decently, why has it been added to Emacs? Isn't it normal
that people use it then and are left with questions when problems occur
and there is no documentation?
Michael.
next prev parent reply other threads:[~2017-11-24 7:04 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
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 [this message]
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=87y3mww419.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=27445@debbugs.gnu.org \
--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).