Re: [Bug: 21.5-b32] Hyper Apropos confused about user variables, sometimes eats first letter of docstring
Mike Kupfer writes:
If you mean byte-compile-dynamic-docstrings, yes, that's set to t
(the
default). Setting it to nil prior to loading Gnus doesn't help.
No, it won't. You would need to recompile Gnus, if this is the right
explanation.
The other related possibility I can see is that the elc got corrupted
by the insertion of an extraneous byte somehow.
I tried M-x apropos, and I see related behavior for the same set of
variables.
How about C-h v?
So here's my guess at the problem:
gnus-adaptive-word-no-group-words is
being treated as a user variable because it's defined by defcustom. So
Hyper Apropos is assuming that the docstring starts with "*" and
helpfully deleting the docstring's first character before displaying it.
Does that sound plausible? If yes, what's the right fix?
It could be right. Someone would have to check the code that does the
parsing in hyper-apropros to find out. Me, I'm taking two aspirin and
going to bed. Call me in the morning. :-)
However, it's strange that you don't observe this anywhere else, and
nobody else does, if that's the problem. The issue of defcustoms not
corresponding exactly to old-style starred "user variables" is not
unique to Gnus.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta