unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Lars Magne Ingebrigtsen'" <larsi@gnus.org>
Cc: 2030@debbugs.gnu.org
Subject: bug#2030: 23.0.60; doc string of dired-guess-shell-alist-user
Date: Sat, 16 Jul 2011 16:21:38 -0700	[thread overview]
Message-ID: <057DB3F3B113413AA463B2C0902C846C@us.oracle.com> (raw)
In-Reply-To: <m3mxget6oc.fsf@quimbies.gnus.org>

> I disagree, and I'm closing this report.

Then please change the status from `fixed' to `wontfix', Lars.

You did not fix anything that was reported.

And there were several points raised - all ignored.  ("\\.bar\'" to "\\.bar\\'"
had apparently already been corrected.)  You even left the inappropriate
uppercase for the fictitious command names.

All you did AFAICT was change the calls to `list' to a quoted list constant - no
relation to the bug report.  Worse - part of the bug report was precisely that
there is no sense in showing an example with `setq', especially if the value is
a _constant_.

There is no reason to show _setting_ the value - in any way.  It is fine to show
an example value though (provided it is cleaned up, as suggested), if it helps
to understand the structure etc.  But no reason to show how to set it.

If for some reason (and there is none here) we did need to mention how to set
this option's value, then general Emacs policy calls for privileging Customize
in the doc.

You not only insisted that the doc string show how to set the value (useless),
but that it continue to do so using `setq' - not even `customize-set-variable'.
The reason you gave was that users will want to copy+paste this `setq'
expression.  Hard to believe.

It's your prerogative not to fix the bug, but in that case please change the
status to `wontfix'.  Thank you.






      reply	other threads:[~2011-07-16 23:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-24 19:09 bug#2030: 23.0.60; doc string of dired-guess-shell-alist-user Drew Adams
2011-07-11 13:48 ` Lars Magne Ingebrigtsen
2011-07-11 15:19   ` Drew Adams
2011-07-11 15:21     ` Lars Magne Ingebrigtsen
2011-07-11 16:03       ` Drew Adams
2011-07-16 18:35         ` Lars Magne Ingebrigtsen
2011-07-16 23:21           ` Drew Adams [this message]

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=057DB3F3B113413AA463B2C0902C846C@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=2030@debbugs.gnu.org \
    --cc=larsi@gnus.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).