unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Emacs-Devel devel <emacs-devel@gnu.org>,
	Drew Adams <drew.adams@oracle.com>, Miles Bader <miles@gnu.org>
Subject: Re: `set-variable' should use :set
Date: Sat, 23 Oct 2010 13:48:51 +0900	[thread overview]
Message-ID: <87vd4tjyz0.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <AANLkTinc1qbPwZ6AuoD-1pqHwU4Q=MNT0ezs=-hzP0QV@mail.gmail.com>

Juanma Barranquero writes:

 > > Most important is clarity, and I find "However, this feature is
 > > largely obsoleted by `defcustom'" quite clear as far as it goes
 > > (it doesn't say why or how).
 > 
 > I find it quite clear too.

Clear, yes.  I personally think it's ugly and awkward, the kind of
usage a tasteless engineer[1] would invent.  I would hope that Emacs
aspires to a higher, more literary standard.  That's why I suggested
Drew contribute a patch, not as an indirect way of asking him to shut
up.  (The smiley was because I expected the response he produced: a
few hundred words on emacs-devel and no patch.)

I don't think that clarity is sufficiently important that we should
say "if it's clear, ship it."  Precision in natural language is as
important as precision in formal languages.  I don't have an issue
with efficient use of one's time; if you happen to be a tasteless
engineer, your contribution will be in elegant code, not elegant
docs.  Clarity is the sine qua non, and that's what you should aim for
if getting even that is a struggle.

But a superior application will have elegant docs, which the user will
appreciate far more than elegant code.  (Of course neither holds a
candle to elegant UI.)

Footnotes: 
[1]  The adjective is not redundant.





  reply	other threads:[~2010-10-23  4:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-21 17:25 `set-variable' should use :set Drew Adams
2010-10-22  0:34 ` Miles Bader
2010-10-22  0:48   ` Miles Bader
2010-10-22  1:11     ` Drew Adams
2010-10-22  2:20       ` Stephen J. Turnbull
2010-10-22  4:34         ` Drew Adams
2010-10-22  7:17           ` Stephen J. Turnbull
2010-10-22  8:29             ` David Kastrup
2010-10-22 10:43           ` Juanma Barranquero
2010-10-22 13:40             ` Drew Adams
2010-10-22 14:02               ` David Kastrup
2010-10-22 22:42               ` Juanma Barranquero
2010-10-23  4:48                 ` Stephen J. Turnbull [this message]
2010-10-23 16:13                   ` Drew Adams
2010-10-23 17:47                     ` Juanma Barranquero
2010-10-23 18:44                       ` Glenn Morris
2010-10-23 19:01                       ` Jambunathan K
2010-10-24 16:15                       ` Chong Yidong
2010-10-22 14:01           ` Stefan Monnier
2010-10-22 16:03             ` Drew Adams
2010-10-22  7:42         ` Eli Zaretskii
2010-10-22  7:39       ` Eli Zaretskii
2010-10-22  8:16         ` Stephen J. Turnbull
2010-10-22  9:46           ` 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=87vd4tjyz0.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    --cc=miles@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).