From: Robert Thorpe <rt@robertthorpeconsulting.com>
To: f.nikolakopoulos@gmail.com
Cc: help-gnu-emacs@gnu.org
Subject: Re: clhs on other languages
Date: Tue, 21 Nov 2017 00:43:25 +0000 [thread overview]
Message-ID: <87mv3gjwb6.fsf@robertthorpeconsulting.com> (raw)
In-Reply-To: <87efovbaaq.fsf_-_@hp-laptop> (f.nikolakopoulos@gmail.com)
f.nikolakopoulos@gmail.com writes:
> is any analogous inside emacs like clhs help on slime lisp environment in other
> languages like c/c++, python or fortran for command reference and syntax
There is nothing directly comparable. However, are you aware of "C-h S"
(Info-lookup-symbol)?
For example, open a file in C mode. Go to a function and press "C-h
S". It will find the documentation for that function. For this to work
you have to have the Info documentation for GNU Libc installed.
It works for other languages too if you install an Info file that
contains documentation for the language or library in question. On my
system it works for C, Bash and Emac Lisp (I haven't any other languages
installed). I expect installing the GNU Fortran Info docs will make it
work in Fortran mode. I think the same thing will be true of Python
too.
Some languages don't support Info or provide compatible docs. However,
if you look on the internet there are sometimes unofficial info docs
that will make this feature work.
BR,
Robert Thorpe
next prev parent reply other threads:[~2017-11-21 0:43 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3764.1510787840.27995.help-gnu-emacs@gnu.org>
2017-11-16 7:04 ` Transposing words over middle words Loris Bennett
2017-11-16 8:41 ` Joost Kremers
2017-11-16 8:47 ` Joost Kremers
2017-11-16 16:06 ` Eli Zaretskii
2017-11-16 22:26 ` Bob Proulx
2017-11-17 5:00 ` Yuri Khan
2017-11-17 5:08 ` Emanuel Berg
2017-11-17 8:55 ` Gian Uberto Lauri
2017-11-17 8:58 ` Gian Uberto Lauri
2017-11-17 9:10 ` Eli Zaretskii
2017-11-17 9:35 ` Gian Uberto Lauri
2017-11-17 16:03 ` Stefan Monnier
2017-11-17 16:19 ` Robert Pluim
2017-11-17 20:41 ` Marcin Borkowski
2017-11-17 16:42 ` Eli Zaretskii
2017-11-17 22:53 ` Stefan Monnier
2017-11-17 23:02 ` Emanuel Berg
[not found] ` <mailman.3897.1510936953.27995.help-gnu-emacs@gnu.org>
2017-11-17 16:57 ` Rusi
2017-11-17 17:26 ` Drew Adams
2017-11-17 18:05 ` Eli Zaretskii
2017-11-17 22:55 ` Stefan Monnier
2017-11-17 23:09 ` Emanuel Berg
2017-11-21 17:21 ` Tomas Nordin
2017-11-22 18:18 ` Arnaldo Mandel
2017-11-22 19:15 ` Emanuel Berg
2017-11-22 21:33 ` Stefan Monnier
2017-11-17 20:38 ` Marcin Borkowski
2017-11-18 17:11 ` Robert Thorpe
2017-11-16 21:55 ` Michael Piotrowski
2017-11-16 23:05 ` Joseph C. Fineman
2017-11-17 0:39 ` Emanuel Berg
2017-11-17 7:19 ` Eli Zaretskii
2017-11-18 20:29 ` clhs on other languages f.nikolakopoulos
2017-11-21 0:43 ` Robert Thorpe [this message]
[not found] ` <mailman.3847.1510879170.27995.help-gnu-emacs@gnu.org>
2017-11-17 23:34 ` Transposing words over middle words Joseph C. Fineman
2017-11-18 0:05 ` Emanuel Berg
[not found] ` <mailman.3932.1510963563.27995.help-gnu-emacs@gnu.org>
2017-11-18 22:55 ` Joseph C. Fineman
2017-11-18 23:57 ` Emanuel Berg
[not found] ` <mailman.3856.1510903218.27995.help-gnu-emacs@gnu.org>
2017-11-17 23:35 ` Joseph C. Fineman
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=87mv3gjwb6.fsf@robertthorpeconsulting.com \
--to=rt@robertthorpeconsulting.com \
--cc=f.nikolakopoulos@gmail.com \
--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).