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

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

bug#22448: 24.5; `M-x customize' link "See als Manual"


From: Stefan Kangas
Subject: bug#22448: 24.5; `M-x customize' link "See als Manual"
Date: Wed, 06 Nov 2019 02:08:53 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)

Drew Adams <drew.adams@oracle.com> writes:

>> > The link near the top of the buffer says See also Manual.
>> > Clicking that link should take you to the part of the Emacs
>> > manual that presents Customize.  Instead, it takes you to
>> > the top of the manual.  That's not helpful at all.
>> 
>> There are three links to the manual, actually.  Please see the attached
>> screenshot.  The "See also" link is for the top-level `Emacs' group.
>
> The other two links are fine.  The link I reported is wrong.
> Even if it is intended to be relevant to group `Emacs', it is
> wrong.  Group `Emacs' is a Customize group.  The link does not
> take you anywhere that provides information about Customize
> groups in general or any Customize group in particular, let
> alone the `Emacs' group.
>
> In addition, there already is an "Emacs manual" link to the
> top of the manual.  There is no need for another.
>
> The problematic link should just be removed, if there is no
> doc specific for group `Emacs' to which it could be linked.
> It does not help, but confuses, as it is now.

Thank you Drew for your attention to detail.  Please find some of my
observations below.

I don't think this link causes any confusion.  On the contrary, it is
a clear indication to users that they should read the Emacs manual if
they want help with customizing Emacs.

This adds more information than the blanket "For help using this
buffer, see Easy Customization in the Emacs manual." which is already
at the top of every Custom buffer.  It is therefore fully suitable,
and indeed directly helpful, for the first entry in the M-x customize
interface (the emacs group).

So I would suggest to keep the link as is, and consequently close this
bug as wontfix.  But perhaps others will have an opinion here, too.

Best regards,
Stefan Kangas





reply via email to

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