unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Nicolas P. Rougier (inria)" <nicolas.rougier@inria.fr>
To: Eli Zaretskii <eliz@gnu.org>
Cc: casouri@gmail.com, emacs-devel@gnu.org
Subject: Re: Question on set-window-margins
Date: Wed, 03 Jan 2024 15:05:13 +0100	[thread overview]
Message-ID: <m27ckqv76y.fsf@inria.fr> (raw)
In-Reply-To: <834jfuzhg1.fsf@gnu.org>


Eli Zaretskii [2024-01-03 at 15:15] wrote:
> I added that, but I'm always surprised by people jumping to
> conclusions without studying both the relevant doc string(s) and 
> the
> relevant descriptions in the manual.  Doc strings and the 
> manuals have
> different purposes and different size limitations, so it's
> unreasonable to expect only one of them to include all of the
> important information, let alone that of secondary importance,
> caveats, etc.
> 
> Please always look up the functions you are interested in both 
> in the
> built-in help and in the manual, before you conclude that 
> something is
> strange or undocumented.

Well noted. But the manual needs some modification as well 
(suppressing "full"):

4.1 Finding More Information:

If you are interested, you can get the full documentation of any 
Emacs Lisp function at any time by typing C-h f and then the name 
of the function (and then RET). Similarly, you can get the full 
documentation for a variable by typing C-h v and then the name of 
the variable (and then RET). 

Nicolas

-- 
Nicolas P. Rougier —— www.labri.fr/perso/nrougier
Institute of Neurodegenerative Diseases, Bordeaux



  reply	other threads:[~2024-01-03 14:05 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) [this message]
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
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=m27ckqv76y.fsf@inria.fr \
    --to=nicolas.rougier@inria.fr \
    --cc=casouri@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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.
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).