emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#55904: closed (29.0.50; Docstring in Help vs. Customize buffer)


From: GNU bug Tracking System
Subject: bug#55904: closed (29.0.50; Docstring in Help vs. Customize buffer)
Date: Sat, 11 Jun 2022 10:32:02 +0000

Your message dated Sat, 11 Jun 2022 13:31:18 +0300
with message-id <83ilp7xzih.fsf@gnu.org>
and subject line Re: bug#55904: 29.0.50; Docstring in Help vs. Customize buffer
has caused the debbugs.gnu.org bug report #55904,
regarding 29.0.50; Docstring in Help vs. Customize buffer
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
55904: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=55904
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: 29.0.50; Docstring in Help vs. Customize buffer Date: Sat, 11 Jun 2022 12:16:48 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50
Hi all,

I see a mismatch between the docstring of a custom variable shown in the
Help buffer and in the Customize buffer.  To reproduce:

  • emacs -Q
  • M-x load-library RET whitespace RET
  • C-h v whitespace-action RET
  • Look at the docstring which look Ok
  • Hit the customize button which looks like this

PNG image

Note the extra indentations after nil and autocleanup.

I don't use customize very often so this is the first time I'm seeing
this.  This is with Emacs 29 from master (0fd60451bc).

Best, Arash

--- End Message ---
--- Begin Message --- Subject: Re: bug#55904: 29.0.50; Docstring in Help vs. Customize buffer Date: Sat, 11 Jun 2022 13:31:18 +0300
> From: Arash Esbati <arash@gnu.org>
> Date: Sat, 11 Jun 2022 12:16:48 +0200
> 
>   • emacs -Q
>   • M-x load-library RET whitespace RET
>   • C-h v whitespace-action RET
>   • Look at the docstring which look Ok
>   • Hit the customize button which looks like this
> 
> Note the extra indentations after nil and autocleanup.

This is because the doc string included TABs.  Now fixed on the
release branch.

Thanks.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]