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>
Cc: 14734@debbugs.gnu.org
Subject: bug#14734: 24.3.50; REGRESSION: defadvice broken wrt doc strings (C-h f)
Date: Fri, 28 Jun 2013 10:39:54 -0700 (PDT)	[thread overview]
Message-ID: <c6e75742-6033-40ff-8fd4-79e190eefa8b@default> (raw)
In-Reply-To: <9cf39b5d-d100-4b72-bf78-95f6cee0d8c0@default>

> > If you don't want to see the internal thingy, then use the new
> > advice-add rather than the old defadvice.

So you introduce a regression in user-visible behavior that
degrades the user interface, with the idea that that will
encourage use of your new advice replacement over traditional
defadvice?  Is that it?

Using traditional advice to add to a doc string has always worked
seamlessly: a user saw a single display of help text that included
both the original doc and any doc added by advice, seamlessly.

The change introduced is horrible for users.  Now they see only
the original doc string, plus a link that will be incomprehensible
to many (so skipped over by them):

  :around advice: `ad-Advice-isearch-forward'

And if they do happen to click that uninviting link then they
get an even more incomprehensible page of internal,
advice-oriented code and unintelligible text:

  ad-Advice-isearch-forward is a Lisp function.

  (ad-Advice-isearch-forward AD--ADDOIT-FUNCTION &optional REGEXP-P
  NO-RECURSIVE-EDIT)

  Advice function assembled by advice.el.

  Before-advice `isearch+-doc':
   
  Isearch Plus
  ============
  ...

What they should see for `C-h f isearch-forward', and what they have
always seen in the past, is the original `isearch-forward' doc together
with the added doc from advising - it is just appended:

  Isearch Plus
  ============
  ...

Emacs did that by design.  You have broken that.

Not only can Emacs do better, it always HAS.  This is a real step
backward for users.  Intentional or not.  I'm reopening the bug.
I hope you will seriously consider reverting the misguided changes
that introduced this regression.





  reply	other threads:[~2013-06-28 17:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 17:08 bug#14734: 24.3.50; REGRESSION: defadvice broken wrt doc strings (C-h f) Drew Adams
2013-06-27 18:15 ` Stefan Monnier
2013-06-27 18:40   ` Drew Adams
2013-06-28 17:39     ` Drew Adams [this message]
2013-06-28 20:44       ` Dmitry Gutov
2013-06-28 21:56         ` Drew Adams
2013-06-28 22:19           ` Michael Heerdegen
2019-09-23 21:07         ` bug#13581: " Lars Ingebrigtsen
2013-06-28 22:27   ` Michael Heerdegen
2013-06-28 23:21     ` Stefan Monnier
2013-06-29  1:37       ` Drew Adams
2013-06-29  2:09         ` Stefan Monnier
2013-06-29  2:28           ` Drew Adams
2013-06-29  3:24             ` Stefan Monnier
2013-06-29 20:29               ` Juanma Barranquero
2013-06-30  1:39                 ` Stefan Monnier
2013-07-05 14:50                   ` Drew Adams
2013-07-05 14:57                     ` Juanma Barranquero
2013-07-05 22:44                     ` Stefan Monnier
2013-07-06  1:40                       ` Drew Adams
2013-07-06  9:18                         ` Stefan Monnier
2013-07-06 20:22                           ` Drew Adams
2013-10-20 23:27               ` 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=c6e75742-6033-40ff-8fd4-79e190eefa8b@default \
    --to=drew.adams@oracle.com \
    --cc=14734@debbugs.gnu.org \
    --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).