From: Thien-Thi Nguyen <ttn@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: window--dump-frame
Date: Fri, 23 May 2014 09:32:28 +0200 [thread overview]
Message-ID: <87lhtthrw3.fsf@zigzag.favinet> (raw)
In-Reply-To: <jwvoaypo773.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 22 May 2014 17:06:09 -0400")
[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]
() Stefan Monnier <monnier@IRO.UMontreal.CA>
() Thu, 22 May 2014 17:06:09 -0400
No, "--" means it's "internal", but it's perfectly OK to have
commands designed solely for debugging purposes, i.e. "internal use".
Sure, for the programmer. Unfortunately, the distinction is not readily
comprehensible (and more to the point, respected) by the non-programmer.
If it shows up in ‘apropos-command’, it will be tried and maybe trusted.
Betraying the trust, for reasons even justifiable, is Not Cool.
I stand by my gut feelings: Best to avoid "don't do that" in a future
mailing list post by not making "that" doable. Next best would be to
add hugely fearsome disclaimers in the docstring, i suppose. Then
"don't do that" becomes "RTFM", which is only slightly more mellifluous.
(In times past, i would have optimistically imagined another message:
"read the source, luke!". Maybe that optimism will return, who knows.
No man is an island, but the puddles are damnably prevalent...)
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2014-05-23 7:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 6:27 window--dump-frame Glenn Morris
2014-05-22 7:07 ` window--dump-frame martin rudalics
2014-05-22 15:55 ` window--dump-frame Glenn Morris
2014-05-22 16:18 ` window--dump-frame Thien-Thi Nguyen
2014-05-22 21:06 ` window--dump-frame Stefan Monnier
2014-05-23 7:32 ` Thien-Thi Nguyen [this message]
2014-05-23 13:30 ` window--dump-frame Stefan Monnier
2014-05-23 17:12 ` window--dump-frame Thien-Thi Nguyen
2014-05-23 20:49 ` window--dump-frame Stefan Monnier
2014-05-25 9:28 ` window--dump-frame Thien-Thi Nguyen
2014-05-25 10:09 ` window--dump-frame martin rudalics
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=87lhtthrw3.fsf@zigzag.favinet \
--to=ttn@gnu.org \
--cc=emacs-devel@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 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.