unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>, Alan Mackenzie <acm@muc.de>
Cc: 16491-done@debbugs.gnu.org
Subject: bug#16491: 24.3.50; ?REGRESSION: `defadvice' doc removed from Elisp manual
Date: Sun, 19 Jan 2014 14:32:48 -0800 (PST)	[thread overview]
Message-ID: <ba03439a-e062-4a48-9f2e-77281a6f6c0c@default> (raw)
In-Reply-To: <jwvha8zd7wg.fsf-monnier+emacsbugs@gnu.org>

> >> What's not fine is to simply remove all of the doc about
> >> the traditional `defadvice' advice system.
> 
> Totally agreed.  Which is why I kept the 60KB of docs in the
> Commentary section of advice.el.

That is not the user doc.  It is good that you at least
saved that information somewhere.  Such a concession!  60KB!

But it is not sufficient to just stuff that information into
a Lisp-file Commentary somewhere.  At the very least, it
should be available as an Info manual distributed with Emacs.

The fact that you felt it was worth mentioning how many KB
this doc weighs betrays your attitude about it, and perhaps
about user doc in general.

But you have already expressed yourself on that, stating in
the past that users don't need _any_ doc, and the code needs
no comments - the code itself suffices and is the real doc.
When will you bury all of the doc in Lisp comments?  Why
stop now with `defadvice'?

This is an anti-user attitude that is quite inappropriate,
especially for someone charged with leading Emacs development.
Too bad.

At least I know where to find the `defadvice' doc now - thank
you for that tip.  But poor Emacs.

Oh, BTW, did you give a _reason_ for carving this out of the
doc and moving it to a Lisp comment?  Did you propose that
possibility for emacs-devel discussion and present technical
or user-level arguments supporting it?

Did I miss those reasons somehow?  No?  I didn't think so.





  reply	other threads:[~2014-01-19 22:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.12294.1390113984.10748.bug-gnu-emacs@gnu.org>
2014-01-19  6:45 ` bug#16491: 24.3.50; REGRESSION: `defadvice' doc removed from Elisp manual Drew Adams
2014-01-19 16:58   ` bug#16491: 24.3.50; ?REGRESSION: " Alan Mackenzie
2014-01-19 20:40     ` Stefan Monnier
2014-01-19 22:32       ` Drew Adams [this message]
2014-01-20  2:31         ` Stefan Monnier
2014-01-22 22:11           ` Alan Mackenzie
2014-01-22 22:20             ` Daniel Colascione
2014-01-22 22:42               ` Drew Adams

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=ba03439a-e062-4a48-9f2e-77281a6f6c0c@default \
    --to=drew.adams@oracle.com \
    --cc=16491-done@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=monnier@iro.umontreal.ca \
    /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).