From: Sergey Organov <sorganov@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: c++-mode does not support C-h S?
Date: Mon, 06 Mar 2023 16:13:35 +0300 [thread overview]
Message-ID: <87mt4q81kw.fsf@osv.gnss.ru> (raw)
In-Reply-To: <835ybe83b7.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 06 Mar 2023 14:36:12 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Sergey Organov <sorganov@gmail.com>
>> Date: Mon, 06 Mar 2023 00:11:02 +0300
>>
>> In a buffer with c++-mode major mode, pressing C-h S causes appearance
>> of the prompt "Use symbol help mode: " in the minibuffer that, according
>> to the manual, means c++-mode does not support info-lookup-symbol?:
>>
>> If you use C-h S in a major mode that does not support it, it asks you
>> to specify the symbol help mode. You should enter a command such as
>> c-mode that would select a major mode which C-h S does support.
>
> If you type "c-mode RET" at the prompt, does the feature work then?
Yes, it does. It finds symbols in GNU C library info files alright then.
>
>> How do I configure c++-mode to use c-mode to lookup symbols
>
> Copy the two info-lookup-maybe-add-help blocks in info-look.el that
> reference c-mode and make them reference c++-mode.
Thanks for the hint, will try.
>
>> and why it's not configured this way by default?
>
> Because the _real_ documentation of C++ is usually not installed on
> the end-user systems.
GNU Standard C++ Library v3 (documentation files) are likely to be
installed on Linux hosts, I think.
Also, C library is still accessible from C++, so search in GNU C info
files what was not found in C++ seems to be a good idea as well.
Thanks,
-- Sergey Organov
next prev parent reply other threads:[~2023-03-06 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 21:11 c++-mode does not support C-h S? Sergey Organov
2023-03-06 12:36 ` Eli Zaretskii
2023-03-06 13:13 ` Sergey Organov [this message]
2023-03-06 14:16 ` Eli Zaretskii
2023-03-06 15:49 ` Sergey Organov
2023-03-06 15:56 ` Arsen Arsenović
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=87mt4q81kw.fsf@osv.gnss.ru \
--to=sorganov@gmail.com \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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.
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).