From: npostavs@users.sourceforge.net
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24923@debbugs.gnu.org
Subject: bug#24923: 25.1; Lisp watchpoints
Date: Sun, 20 Nov 2016 12:00:52 -0500 [thread overview]
Message-ID: <87polqjdbv.fsf@users.sourceforge.net> (raw)
In-Reply-To: <83mvgu9m92.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 20 Nov 2016 17:58:17 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> @@ -1233,13 +1233,14 @@ DEFUN ("set", Fset, Sset, 2, 2, 0,
>> If buffer/frame-locality is an issue, WHERE specifies which context to use.
>> (nil stands for the current buffer/frame).
>>
>> - If BINDFLAG is false, then if this symbol is supposed to become
>> - local in every buffer where it is set, then we make it local.
>> - If BINDFLAG is true, we don't do that. */
>> + If BINDFLAG is SET_INTERNAL_SET, then if this symbol is supposed to
>> + become local in every buffer where it is set, then we make it
>> + local. If BINDFLAG is SET_INTERNAL_BIND or SET_INTERNAL_UNBIND, we
>> + don't do that. */
>
> What are those SET_INTERNAL_* values? They are numbers, right? Then
> they should be described as such in the doc string.
They're enum values. Perhaps you were confused by the hunk header?
That's not a doc string, it's the comment on set_internal, a C function.
next prev parent reply other threads:[~2016-11-20 17:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 3:10 bug#24923: 25.1; Lisp watchpoints npostavs
2016-11-11 10:02 ` Eli Zaretskii
2016-11-12 4:34 ` npostavs
2016-11-12 7:19 ` Eli Zaretskii
2016-11-13 0:54 ` npostavs
2016-11-13 15:29 ` Eli Zaretskii
2016-11-20 2:12 ` npostavs
2016-11-20 10:49 ` Stephen Berman
2016-11-20 14:14 ` npostavs
2016-11-20 16:11 ` Eli Zaretskii
2016-11-20 19:26 ` npostavs
2016-11-20 19:36 ` Eli Zaretskii
2016-11-20 20:16 ` npostavs
2016-11-21 17:31 ` Eli Zaretskii
2016-12-03 1:47 ` npostavs
2016-12-03 3:49 ` Clément Pit--Claudel
2016-12-03 3:50 ` Clément Pit--Claudel
2016-12-03 5:01 ` Daniel Colascione
2016-12-03 14:11 ` npostavs
2016-11-20 15:58 ` Eli Zaretskii
2016-11-20 17:00 ` npostavs [this message]
2016-11-20 17:25 ` 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=87polqjdbv.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=24923@debbugs.gnu.org \
--cc=eliz@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).