From: Eli Zaretskii <eliz@gnu.org>
To: Michael Kifer <michael.kifer@stonybrook.edu>
Cc: 16744@debbugs.gnu.org
Subject: bug#16744: 24.3.50; REGRESSION: C-h v does not show doc for `ediff-highlight-all-diffs'
Date: Fri, 14 Feb 2014 13:14:05 +0200 [thread overview]
Message-ID: <83bnyac5fm.fsf@gnu.org> (raw)
In-Reply-To: <52FDF361.5060903@stonybrook.edu>
> Date: Fri, 14 Feb 2014 05:43:45 -0500
> From: Michael Kifer <michael.kifer@stonybrook.edu>
> CC: "16744@debbugs.gnu.org" <16744@debbugs.gnu.org>
>
> This problem is caused by some change in the emacs compiler.
> The reason I was not seeing it is because I was using .elc files of
> my development copy of ediff, which were compiled with an older
> version of emacs. With those .elc's the documentation string was
> being shown.
>
> Perhaps the empty doc-string in defvar now zaps the doc-string
> specified in the preceding defcustom while previously it didn't? If
> so, the previous behavior was smarter.
But why do we need both the defcustom and the defvar in the macro?
next prev parent reply other threads:[~2014-02-14 11:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 19:31 bug#16744: 24.3.50; REGRESSION: C-h v does not show doc for `ediff-highlight-all-diffs' Drew Adams
2014-02-13 20:29 ` Eli Zaretskii
[not found] ` <1913911dabee4a1e979c4914631ac676@HUBCAS2.cs.stonybrook.edu>
2014-02-14 7:53 ` Michael Kifer
2014-02-14 9:22 ` Eli Zaretskii
2014-02-14 10:20 ` Michael Kifer
2014-02-14 10:43 ` Michael Kifer
2014-02-14 11:14 ` Eli Zaretskii [this message]
2014-02-14 19:14 ` Michael Kifer
2014-02-14 20:58 ` Eli Zaretskii
2014-02-14 21:08 ` Glenn Morris
2014-02-14 21:52 ` Michael Kifer
2014-02-14 22:22 ` Glenn Morris
2014-02-14 22:35 ` Michael Kifer
2014-02-14 23:24 ` Michael Kifer
2014-02-16 3:34 ` Glenn Morris
2014-02-15 10:02 ` Andreas Schwab
[not found] <<4d0cbf1a-914e-493c-bb2f-186229902418@default>
[not found] ` <<83txc2dadt.fsf@gnu.org>
2014-02-13 21:01 ` 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=83bnyac5fm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16744@debbugs.gnu.org \
--cc=michael.kifer@stonybrook.edu \
/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).