unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pip Cet via "Emacs development discussions." <emacs-devel@gnu.org>
To: emacs-devel@gnu.org
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: Re: master a427927123c 1/2: ; * src/lisp.h (struct Lisp_Subr): Fix comment.
Date: Wed, 08 Jan 2025 13:55:28 +0000	[thread overview]
Message-ID: <87jzb5e7g2.fsf@protonmail.com> (raw)
In-Reply-To: <20250108134420.91DC0C527A9@vcs2.savannah.gnu.org>

"Eli Zaretskii" <eliz@gnu.org> writes:

> branch: master
> commit a427927123cea5ddbf2f2edc1db69ec7d83f2d42
> Author: Eli Zaretskii <eliz@gnu.org>
> Commit: Eli Zaretskii <eliz@gnu.org>
>
>     ; * src/lisp.h (struct Lisp_Subr): Fix comment.
> ---
>  src/lisp.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/src/lisp.h b/src/lisp.h
> index 4c09afc77e2..c93d4d15b33 100644
> --- a/src/lisp.h
> +++ b/src/lisp.h
> @@ -2228,8 +2228,8 @@ struct Lisp_Subr
>        Lisp_Object native;
>      } intspec;
>      Lisp_Object command_modes;
> -    /* positive values: offset into etc/DOC.  Negative values: one's
> +    /* Positive values: offset into etc/DOC.  Negative values: one's

Thanks!  Sorry about that.

> -       complement of index into the native comp unit's function
> +       complement of index into the native comp unit's function's
>         documentation vector.  */

Every native comp unit has a single vector, which contains its
functions' documentation strings.  It's shared between all functions, so
you can refer to it as the "function's documentation vector".

I didn't, because it sounds (to me) like a different vector is used for
each function.

Pip




       reply	other threads:[~2025-01-08 13:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <173634386029.21517.6056719579983568172@vcs2.savannah.gnu.org>
     [not found] ` <20250108134420.91DC0C527A9@vcs2.savannah.gnu.org>
2025-01-08 13:55   ` Pip Cet via Emacs development discussions. [this message]
2025-01-08 14:07     ` master a427927123c 1/2: ; * src/lisp.h (struct Lisp_Subr): Fix comment Eli Zaretskii

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=87jzb5e7g2.fsf@protonmail.com \
    --to=emacs-devel@gnu.org \
    --cc=eliz@gnu.org \
    --cc=pipcet@protonmail.com \
    /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).