From: Jeremy Bryant <jb@jeremybryant.net>
To: "Nicolas P. Rougier (inria)" <nicolas.rougier@inria.fr>
Cc: Eli Zaretskii <eliz@gnu.org>, casouri@gmail.com, emacs-devel@gnu.org
Subject: Re: Question on set-window-margins
Date: Wed, 03 Jan 2024 21:52:25 +0000 [thread overview]
Message-ID: <87r0iy5bfo.fsf@jeremybryant.net> (raw)
In-Reply-To: <m2jzoqcn9k.fsf@inria.fr>
Nicolas, you may be also interested in the following convenient way to access the
relevant manual (rather than the docstring)
C-h S set-window-margins
Because C-h S is bound to info-lookup-symbol.
"
Look up and display documentation of SYMBOL in the relevant Info manual.
SYMBOL should be an identifier: a function or method, a macro, a variable,
a data type, a class, etc.
"
I hope this is a useful suggestion
"Nicolas P. Rougier (inria)" <nicolas.rougier@inria.fr> writes:
> Eli Zaretskii [2024-01-03 at 19:28] wrote:
>> That's not the manual from which to learn this stuff.
>
> C-h f describe-function
>
> Display the full documentation of FUNCTION (a symbol).
> When called from Lisp, FUNCTION may also be a function object.
>
> Nicolas
next prev parent reply other threads:[~2024-01-03 21:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 17:58 Question on set-window-margins Nicolas P. Rougier (inria)
2024-01-02 19:20 ` Eli Zaretskii
2024-01-02 19:46 ` Nicolas P. Rougier (inria)
2024-01-03 3:23 ` Eli Zaretskii
2024-01-03 3:42 ` Yuan Fu
2024-01-03 5:50 ` Nicolas P. Rougier (inria)
2024-01-03 13:15 ` Eli Zaretskii
2024-01-03 14:05 ` Nicolas P. Rougier (inria)
2024-01-03 16:46 ` Eli Zaretskii
2024-01-03 17:24 ` Nicolas P. Rougier (inria)
2024-01-03 17:28 ` Eli Zaretskii
2024-01-03 17:56 ` Nicolas P. Rougier (inria)
2024-01-03 21:52 ` Jeremy Bryant [this message]
2024-01-04 8:53 ` Nicolas P. Rougier (inria)
2024-01-03 15:11 ` John Yates
2024-01-03 16:49 ` Eli Zaretskii
2024-01-03 20:07 ` [External] : " Drew Adams
2024-01-04 12:29 ` John Yates
2024-01-04 12:52 ` Eli Zaretskii
2024-01-05 0:25 ` Yuan Fu
2024-01-05 8:01 ` Eli Zaretskii
2024-01-06 4:35 ` Richard Stallman
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=87r0iy5bfo.fsf@jeremybryant.net \
--to=jb@jeremybryant.net \
--cc=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=nicolas.rougier@inria.fr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).